logo       

Re: [Bug-gnulib] why no strchr or strrchr?: msg#00075

sysutils.autoconf.general

Subject: Re: [Bug-gnulib] why no strchr or strrchr?

"Oskar Liljeblad" <oskar@xxxxxxxxxxx> writes:

> I understand there's little point in supporting anything < C89. It
> is sad though that autoconf hasn't been updated to match the
> compatibility assumptions of GCC and coreutils/gnulib.

Autoconf has more backward-compatibility constraints in this area than
GCC, coreutils, and gnulib does, as it has to support packages that
still want to port to pre-C89 hosts. My impression is that we are
getting close to dumping support for K&R, but it won't occur before
the next stable Autoconf release.

The first step of any such conversion process, which will be quite a
bit of grunt work I'm afraid, will be to poll the Autoconf users to
see who, if anybody, still needs support for pre-C89 hosts.


"Oskar Liljeblad" <oskar@xxxxxxxxxxx> writes:

> I have until now believed that autoconf and automake
> (autoscan in particular) were perfect in this sense.

Perfection? Autoconf? *splutter*

Now I have to find a rag to clean the coffee off my keyboard....


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise