Molle Bestefich wrote:
> Yeah, you're right, they're cumbersome.
> OTOH, if you do put the keyword outside of the $$ string to make it
> work with #define and friends, it's hard to find the appropriate word
> to remove and replace with a new one. What should one go after? If
> you always remove the first word before the /* $Revision$ */, you'll
> have removed a word too much from the source file the first time a
> revision number is inserted. If you search for a '=' in the same line
> as the keyword and insert after that, it might work in most cases..
> But it's not pretty.
I think you don't know how SubWCRev works. The keyword is replaced, but
*not* in the file the keyword is in but the whole file is written to a
new file with those keywords replaced.
[snip
> As I understood it, this is a completely new feature.
> That's why I want it changed to something else, before projects like
> TSVN start using it and it can't be changed anymore. Why? Because we
> may, just in case, want to have room to be able to be compatible with
> the Subversion syntax in the future. Using ':' in the
> TrueText/FalseText case precludes this option.
> Thanks for proving my point :-)..
TSVN already uses SubWCRev, and we already have other keywords using the
?: notation.
SubWCRev was never even intended to be compatible with the Subversion
keywords. It's something completely different. I've created SubWCRev
*because* the Subversion keywords got replaced in the same file and
*because* I couldn't use them without parsing strings. Otherwise I would
have used those keywords and not written a new app.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Apr 9 19:50:15 2005