On Monday 04 April 2005 22:27, Branko Čibej wrote:
> Ph. Marek wrote:
> >Questions, remarks welcome.
>
> No, no, no, no and no.
>
> This kind of excaping has no place in the option file parser. If you
> need special interpretation of the config values, do it with a set of
> utility functions that modify strings (examples are utf en/decoding and
> XML/URL (un)escaping).
If I understand you correctly you want several places calling the un-escape
function (for auto-props, dir-auto-props, and authentication)?
That's possible, too, but I don't know which places all need that.
> -1. Our config file format was designed to be compatible with Ptyhon's
> ConfigParser format (except for the case-sensitivity, for which I'm
> still bainging my head against convenient walls). Your change breaks
> that compatibility.
Well, there's not much I can do.
We need special characters for svn:ignore _and_ for the auth info
(http://marc.theaimsgroup.com/?l=subversion-dev&m=111175528516724&w=2), so
compatibility _has_ to give somewhere.
Although you're right - if we change the behaviour only for some parts, most
of the config file stays the same. But I don't believe that buys us anything
- if I understand you correctly, a single escape in the config file leads to
parsing problems with Python?
And in my feeling it's much worse to parse some parts of a file this way and
others that way - a standard way would be much better.
BTW: Python has good SVN bindings. Why not add this parser to the bindings, so
that a python module can ask "how would you parse this config file?"
This would make for a clean way in the future, as we'd have a clean API.
> -- Brane
Regards,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 5 08:10:12 2005