[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: arch taglines for emacs

From: Miles Bader
Subject: Re: arch taglines for emacs
Date: 22 Aug 2003 10:47:06 +0900

Florian Weimer <address@hidden> writes:
> #define ARCH_TAG "arch-tag: 53bb84c6-dee0-46c6-a275-2db144993d89"
> This would avoid the problem with placing " */".

Hmmm, using `#define' is also ugly, but it doe avoid the end-delimiter

For compatibility with the proposed new embedded-tag format, it should
actually not include the quotes:

   #define ARCH_TAG arch-tag: 53bb84c6-dee0-46c6-a275-2db144993d89

would be the same as the (proposed) new format:

   /* arch-id: "53bb84c6-dee0-46c6-a275-2db144993d89" */

Presuming Tom thinks it's likely that the `new format' will eventually
come to pass in something like it's current form (or rather with
something like the properties Tom's proposal suggests), I'll probably go
ahead and add the tags using the old format, either using

(1)   /* arch-tag: 53bb84c6-dee0-46c6-a275-2db144993d89


(2)   /* arch-tag: 53bb84c6-dee0-46c6-a275-2db144993d89
         (do not change this comment, even a little bit) */


(3)   #define ARCH_TAG arch-tag: 53bb84c6-dee0-46c6-a275-2db144993d89

or even

(4)   #define DONT_TOUCH arch-tag: 53bb84c6-dee0-46c6-a275-2db144993d89

Presumably in the time until the `new format' gets implemented, the
danger of tags getting inadvertently perturbed is reasonably low, so any
of these is basically fine.

Personally I'm inclined to go with (2), as it's a little less ugly than
the `#define' forms, and hopefully the warning is enough to keep the
newline safe -- and it seems like the best form to have in the code base
in the case that no new embedded-tag format ever gets implemented.

80% of success is just showing up.  --Woody Allen

reply via email to

[Prev in Thread] Current Thread [Next in Thread]