Re: Autoconf 2.50 compatibility.

[Michael Livshin]

Rob Browning <address@hidden> writes:

> Guile's configure.in, etc. are not compatible with autoconf 2.50, but
> I've fixed some, if not all of the problems.  The question is, are the
> fixes appropriate for 1.6?

the Guile tarball is supposed to come with already-made configure
script, isn't it?  so that the users who don't build from CVS don't
care.

I guess it can wait, then. ;)

a related question: do you consider the current snarfer situation
(that it's written in AWK and refuses to work on most of the non-Linux
platforms) as critical?

'cause I have something half-working to replace it.  basically a
contraption that uses grep & sed (hopefully in a portable fashion ;))
to process the CPP output to prepare something like this:

-----> cut <-----------------------------------------

(snarf-set-file-name "socket.c")
(snarf 'primitive   "htons"  "(SCM value)"   1    0    0   99 
'(  
            "Convert a 16 bit quantity from host to network byte ordering.\n"
            "@var{value} is packed into 2 bytes, which are then converted\n"
            "and returned as a new integer."  ))    
(snarf-check-arg-position "value" 1   104)
(snarf 'primitive   "ntohs"  "(SCM value)"   1    0    0   116 
'(  
            "Convert a 16 bit quantity from network to host byte ordering.\n"
            "@var{value} is packed into 2 bytes, which are then converted\n"
            "and returned as a new integer."  ))    
(snarf-check-arg-position "value" 1   121)

-----> cut <-----------------------------------------

as you can see, this is all perfectly valid Scheme syntax.

the part that I haven't yet written is the Scheme program to make .doc
files given the above. ;)

-- 
A CONS is an object which cares.
                -- Bernie Greenberg.