Re: 1,000 year backward compatability of tools

2003-02-19 Thread Thomas E. Dickey
On Wed, 19 Feb 2003, Bob Friesenhahn wrote: On Wed, 19 Feb 2003, John W. Eaton wrote: But now? Do we really have to worry about these old systems? If people enjoy the vintage hardware, then is it that bad if they can only use vintage software on it as well? To install modern software

Re: Libtool 1.4.3

2002-10-08 Thread Thomas E. Dickey
On Tue, 8 Oct 2002, Earnie Boyd wrote: FWIR, Akim and other developers tried hard to maintain [back|bug]ward compatibility. But, some of the incompatibility was ill formed autoconf syntax so that incompatibility wasn't maintained and instead a better parser was put into place. not at all

Re: Libtool 1.4.3

2002-10-08 Thread Thomas E. Dickey
On Tue, 8 Oct 2002, Lars Hecking wrote: Bob Friesenhahn writes: On 8 Oct 2002, Akim Demaille wrote: There is one big question which must be answered first: will it have to be Autoconf 2.13 compatible? I *strongly* suggest that it must not. It should AC_PREREQ 2.54

Re: Libtool 1.4.3

2002-10-08 Thread Thomas E. Dickey
On Tue, 8 Oct 2002, Bob Friesenhahn wrote: On 8 Oct 2002, Akim Demaille wrote: There is one big question which must be answered first: will it have to be Autoconf 2.13 compatible? I *strongly* suggest that it must not. It should AC_PREREQ 2.54 immediately. Then, I'm fine with

Re: Auto-tools Win32 Borland C++ Builder

2001-05-24 Thread Thomas E. Dickey
On Wed, 23 May 2001, Axel Thimm wrote: [...] may be there are some hints whether people have already tried with borland compilers. Let's hope they are reading this list and will step forward to discuss it ;) sure - Borland C is much faster, and checks for errors that gcc doesn't bother to