Re: macro doc inconsistencies

[Gary V . Vaughan]

On Sunday 15 April 2001  4:00 pm, Lars J. Aas wrote:
> On Sat, Apr 14, 2001 at 12:04:37AM -0400, Steven G. Johnson wrote:
> : On Fri, 13 Apr 2001 address@hidden wrote:
> : > On Thu, Apr 12, 2001 at 11:21:03PM -0400, Steven G. Johnson wrote:
> : > > This macro is documented in the manual but I can't seem to find it in
> : > > the source.  Is it obsolete?
> : >
> : > Well spotted!  It's now AC_LIBSOURCES([foo.c, bar.c]).
>
> If we could merge the macro reference documentation with the m4 files and
> get it extracted automatically, it would be a breeze to keep the doc
> consistent with the implementation, and since the doc would be located
> with the macro it would be more tempting to update the documentation when
> we're working on a macro.  Creating an "autodoc" system for this wouldn't
> be trivial though, as you need to consider macro ordering for the texi
> document, etc.
>
> Just an idea.  Should I put it in TODO or something?
>
>   Lars J

I almost dare to mention that I have a gawk script that will already more or 
less do this -- it ships with snprintfv, available from my homepages.  But 
then I thought better of it and decided not to since I'd probably be 
flamed... even if I volunteered to tweak it as necessary to make it work with 
m4 input files.

Anyway, having (not) said that, I am all for document extraction.

Cheers,
        Gary.
-- 
  ___              _   ___   __              _         mailto: address@hidden
 / __|__ _ _ ___ _| | / / | / /_ _ _  _ __ _| |_  __ _ ___       address@hidden
| (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \
 \___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/
home page:  /___/                      /___/                  gpg public key:
http://www.oranda.demon.co.uk           http://www.oranda.demon.co.uk/key.asc