Re: autotools and programming style (was: Remove cdrtools)

2006-08-15 Thread Mark Brown
On Tue, Aug 15, 2006 at 02:11:21PM -0500, Steve Greenland wrote: > No, you don't #ifdef all the users, you write multiple versions of a a > generic function that hides the differences, and compile the appropriate > one. Read the reference I gave. > Sure, you *could* do this with autoconf driving

Re: autotools and programming style (was: Remove cdrtools)

2006-08-15 Thread Steve Greenland
On 14-Aug-06, 17:32 (CDT), Hendrik Sattler <[EMAIL PROTECTED]> wrote: > Am Montag 14 August 2006 23:27 schrieb Steve Greenland: > > The *real* problem with the whole autotools disaster is that it promotes > > a braindead idea of how to achieve portability: a #ifdef branch for > > every different s

Re: autotools and programming style (was: Remove cdrtools)

2006-08-14 Thread Nathanael Nerode
Hendrik Sattler wrote: > You mean the difference between manpages-posix-dev (in non-free) and > manpages-dev (in main)? The first is not proposed by Debian (I still don't > get why anone would want to change a standards document as not changing it > is the whole purpose of its existence.) In order

autotools and programming style (was: Remove cdrtools)

2006-08-14 Thread Hendrik Sattler
Am Montag 14 August 2006 23:27 schrieb Steve Greenland: > On 14-Aug-06, 15:59 (CDT), Michael Poole <[EMAIL PROTECTED]> wrote: > > Wouter Verhelst writes: > > > In the case of autotools, the fact is that usually it's configure.ac or > > > Makefile.am being horribly broken, rather than the autotools.