On Sat, Oct 13, 2001 at 09:44:46PM +0200, Guido Draheim wrote:
> [EMAIL PROTECTED] wrote:
> > Of course but i can't go back. The ability to declare variables
> > anywhere is fantastic. i'm not even tempted to use C++ anymore. :-)
>
> if only I had enough time to work and extend the substruct-c
> Date: Tue, 9 Oct 2001 10:14:17 +0200
> From: Holger Veit <[EMAIL PROTECTED]>
> > AC_CHECK_LIB(cposix,strerror)
> > ...
> > But please don't ask me why AC_CHECK_LIB successes on OS/2 while it
> > fails on Linux (both don't have a cposix).
>
> This test is Linuxish-only, and entirely WRONG!
We'
On Sat, Oct 13, 2001 at 09:07:54PM +0200, Guido Draheim wrote:
> make a macro (after AC_PROG_CC) that includes a check like
> TESTC99DECLARATIONS
> if notOK and test $GCC = yes ::
> save_CFLAGS="$CFLAGS"
> CFLAGS="$CFLAGS -std=gnu99"
> TESTC99DECLARATIONS
> if stillnotOK ::
> CFLAGS=s
[EMAIL PROTECTED] wrote:
> {..}
> Is this stylistically acceptable?
*fg* oh well, speaking about style is (of course) a matter of taste
and then a matter of whose taste it shall please. For a macro that
you want to reuse in your own projects, yes looks good.
Speaking as a maintainer of the (gnu
I like to pass certain flags, such as `-Wall', to the C++ compiler in
all the directories of my package. Originally I had `CXXFLAGS=-Wall'
in each of the Makefile.ams, but that duplication seemed wrong, and I
sought a cleaner way to do it. I haven't yet found one.
Here's how I'm now doing it, w
