> Keywords are normally inserted in comment sections. Does your
> file not have such a concept?
Unfortunately it does not work because of the language we use perform a
preprocessing of the input code detecting as input params all strings
starting with a $ symbol no matter if they are included into a comment line
(don't tell me this is a quite "singular" approach.... I agreee
completely...!)
> -----Original Message-----
> From: Erik Huelsmann [mailto:ehuels@gmail.com]
> Sent: Thursday, 26 July, 2007 13:37
> To: roberto.devecchi@vi-grade.com
> Cc: users@subversion.tigris.org
> Subject: Re: alternative keyword substitution notation
>
> On 7/26/07, roberto de vecchi <roberto.devecchi@vi-grade.com> wrote:
> >
> > Within our organization we need to manage file in which the
> $ symbol
> > is recognized as a special character (function parameters
> for example
> > are declared in this way). My goal would be to be able to
> enable the
> > keyword substitution for these files but to make this possibile I
> > would need a way to use a different notation (based on a different
> > symbol) to describe the anchor text.
> >
> > does someone have any kind of suggestion about it? From my point of
> > view also a key like \$Rev\$ would work but currently svn is not
> > recognizing it (of course!)
>
> Keywords are normally inserted in comment sections. Does your
> file not have such a concept?
>
> Another solution is to have the expanded keyword in a string:
>
> $version = "$Rev$"
>
> HTH,
>
> Erik.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 26 13:42:00 2007