<div dir="ltr"><div class="gmail_quote">On Tue, Oct 18, 2011 at 12:50 PM, Oleg Goldshmidt <span dir="ltr"><<a href="mailto:pub@goldshmidt.org">pub@goldshmidt.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">> I understood that, and it's still unstable. Since if some young team member<br>
> not aware of the $Id: trick, will write:<br>
> log("$Id: %d $Name: %s\n",id,name)<br>
> ident will return garbage.<br>
<br>
</div>Someone may alter keyword expansions just before the build, too.<br></blockquote><div><br></div><div>I'm not sure I understand your comment. Are you telling that this is unlikely? I agree, this is not a very big point.</div>
<div><br></div><div>Another reason it's more stable, is, that it never allow the optimizer to mess with your ident strings.</div><div>Any conforming compiler MUST let you see all files used in the executable.</div><div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> If you have documented way to get the ident strings, it's more stable.<br>
<br>
</div>The whole point is to have these strings everywhere, otherwise they<br>
are not very useful. This means the whole development team is aware of<br>
and uses the convention.<br></blockquote><div><br></div><div>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.</div>
<div><br></div></div></div>