Re: [Gnu-arch-users] Re: tagline robustness

[Juri Linkov]

Bruce Stephens <address@hidden> writes:
> >>      static char archid[] = "$Arch: 53bb84c6-dee0-46c6-a275-2db144993d89$";
> 
> As has probably been pointed out, this is likely to be useless.  In
> RCS, things like $Id$ are useful because they change, so doing "ident"
> on binaries tells you something useful about the source from which
> they were built.  But in arch, the tag almost certainly doesn't tell
> you anything that you didn't already know, so being able to embed it
> in binaries isn't useful.  As far as I can see, anyway.  
> 
> Being able to embed revision information into binaries *is* useful,
> but Tom's trick of doing that in configure seems the right way to do
> it.

I agree that embedding arch tags into binary might be useless. I
showed this example only to demonstrate that tag syntax should be
language-independent.  This can be achieved by enclosing tags by some
fixed characters that will work for any syntax of source files:

     /* $Arch: 53bb84c6-dee0-46c6-a275-2db144993d89$ C */
     ;; $Arch: 53bb84c6-dee0-46c6-a275-2db144993d89$ Lisp
     #  $Arch: 53bb84c6-dee0-46c6-a275-2db144993d89$ Perl

But you may also consider the using of XML tags for arch explicit tagging:

     /* <Arch id="53bb84c6-dee0-46c6-a275-2db144993d89"> */

This also provides the unambiguous tag delimiters.

-- 
http://www.jurta.org/emacs/