On Tue, Oct 18, 2011 at 12:50 PM, Oleg Goldshmidt <p...@goldshmidt.org>wrote:
> > I understood that, and it's still unstable. Since if some young team
> member
> > not aware of the $Id: trick, will write:
> > log("$Id: %d $Name: %s\n",id,name)
> > ident will return garbage.
>
> Someone may alter keyword expansions just before the build, too.
>
I'm not sure I understand your comment. Are you telling that this is
unlikely? I agree, this is not a very big point.
Another reason it's more stable, is, that it never allow the optimizer to
mess with your ident strings.
Any conforming compiler MUST let you see all files used in the executable.
>
> > If you have documented way to get the ident strings, it's more stable.
>
> The whole point is to have these strings everywhere, otherwise they
> are not very useful. This means the whole development team is aware of
> and uses the convention.
>
I didn't understand how, eg, my C++ scheme don't work. I think it should
work even if you're including the $Id$ strings in the headers files.
_______________________________________________
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
