[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] SubWCRev update

From: Molle Bestefich <molle.bestefich_at_gmail.com>
Date: 2005-04-09 19:43:00 CEST

I wrote:
>> If you replace "$WCREV$" with "7777", then you can use it in a #define.
>> But if you replace it with "$WCREV: 777$", then the define is not a
>> number but a string, which you'd have to parse and convert it into a
>> number first before you can use it somewhere else.
> That's the sacrifice you have to make if you want to keep both the
> attribute tag and the revision information (whatever) in the file at
> the same time.
> I think the Subversion folks might have chosen a bad replacement
> algorithm since it's not compatible with #defines, but I think they're
> at least right with the "keep everything in one file" style..

Actually, it might not be right for SubWCRev, since it's field of
application is not to pull files in/out of SCM, but to produce
intermediate files that are suitable for automated build processes.
Realizing stuff as I go along :-)..

>> The colon is standard C/C++ syntax. So it's not something we just invented.
>> I think SubWCRev.exe should keep working the way it does now. Otherwise
>> we couldn't even use it anymore in TSVN for the build process without
>> writing scripts to parse those strings instead of clean numbers.

Is this sentence out of context? If by "keep working the way it does"
you mean "keep replacing the entire word instead of doing keywords the
Subversion way", I think you're right. Sorry if I misunderstood you.

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:43:17 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.