[Top][All Lists]

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

Re: RFC: 77-gary-diagnose-version-mismatch.patch

From: Gary V. Vaughan
Subject: Re: RFC: 77-gary-diagnose-version-mismatch.patch
Date: Mon, 02 Feb 2004 10:49:49 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030925 Thunderbird/0.3

Hash: SHA1

Alexandre Duret-Lutz wrote:
| Note that if AC_LIBTOOL_TAGS is removed, both CVS Autoconf and
| CVS Automake need to be changed.  This is not problem, since
| none of them has been released yet... but the sooner you settle
| on this the better :)

Good point.  I guess we need to put that on the 1.6 feature list.  (We could
really do with a libtool bugzilla to manage this kind of thing!!).

| As far as Automake is concerned, AC_LIBTOOL_TAGS is more useful
| because that way it can trace the list of supported tags.  With
| LT_INIT_LIBTOOL it would get a list of options, with some tags
| intermixed.  That could be used too, but it sounds less clean.

I'm all for cleaning up libtool's namespace pollution, but it makes sense to
match out the tag names, and call _LT_TAGS (or whatever AC_LIBTOOL_TAGS
replacement is called).  You would be able to trace that macro for the list of
tag names used.

| It easy: _?(AC|AH|AS|AU|m4)_* macro names are reserved for
| Autoconf, and _?AM_* names are reserved for Automake.  Ideally
| nobody else should define macros in these namespaces, but
| everybody does.

Libtool started to use LT_AC_ for public macros so that the unexpanded ones
would be detected by autoconf (by virtue of the AC_).  We seem to have gotten
confused along the way, so some use that convention and some don't.  The
m4_pattern_forbid call nom allows us to catch _?(LT_)[A-Z_]* as unexpanded
macros, so there is no reason for us to have a messy namespace anymore.
AU_DEFUN can help with the Great Renaming :-)

- --
Gary V. Vaughan      ())_.  address@hidden,}
Research Scientist   ( '/
GNU Hacker           / )=
Technical Author   `(_~)_
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -


reply via email to

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