[Top][All Lists]

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


From: Lars J. Aas
Subject: Re: BUGS
Date: Tue, 23 Jan 2001 17:09:00 +0100
User-agent: Mutt/1.2.5i

On Tue, Jan 23, 2001 at 04:57:26PM +0100, Akim Demaille wrote:
: >>>>> "Kevin" == Kevin Ryde <address@hidden> writes:
: Kevin> Maybe a compromise would be to only ignore when the # is at the
: Kevin> start of the line.  I guess it's very difficult to be sure a #
: Kevin> in the middle is a comment, what with $# or quoting etc.
: The previous problem we had was in a #include line.
: I'm really in favor of scanning comments too.  I browsed several
: configures, and most macro names in comments where from Autoconf per
: se, not from user macros.  My personal opinion is that the advantages
: of catching bad problems outweighs the few problems people will meet
: the first time they see autoconf warn about macro names in comments.
: An additional warning unset by default seems to weak a protection to
: me.  It should be the same warning as for configure code.

Can't we define a convention for refering to macros in comments,

# this test should really be in {AC_PROG_PERL}

or something similar?  <>, @@, $$, (), ::, __ etc.
Then we get the best of both worlds...

  Lars J
Innovation is one percent inspiration and ninetynine percent perspiration,
and in my case; twice that...  -- Norville Barnes, `The Hudsucker Proxy'

reply via email to

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