[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Compile error in current CVS, src/server.c:5500

From: Mark D. Baushke
Subject: Re: Compile error in current CVS, src/server.c:5500
Date: Mon, 21 Jul 2003 13:33:12 -0700

Derek Robert Price <derek@ximbiot.com> writes:

> Mark D. Baushke wrote:
> Ah, good.  That's what I wanted to know.  What do you say to adopting
> this style as a CVS standard:
>     function( "first line\n"
>               "second line\n"
>               "third line\n"
>               ...
> with the option of breaking lines when it feels appropriate.  The
> syntax I'm trying to avoid, again, is:
>     function( "first line\n\
> second line\n\
> third line"
> I'll change HACKING if there is a consensus.

That approach seems reasonable to me.
> I believe the consensus was to follow GNULIB to C89 support, and
> GNULIB recently dropped K&R in favor of C89.


> Incidentally, are there any other headers we check for in the call to
> AC_CHECK_HEADERS in configure.in that we can assume in C89?
> stdbool.h, stddef.h, limits.h, float.h, and stdarg.h were already
> mentioned in the GNULIB forum.


Section 7.1.2 Standard headers

  Each library function is declared in a header, whose contents are made
  available by the #include preprocessing directive. The header declares
  a set of related functions, plus any necessary types and additional
  macros needed to facilitate their use.

  The standard headers are:

    <assert.h>  <locale.h>      <stddef.h>
    <ctype.h>   <math.h>        <stdio.h>
    <errno.h>   <setjmp.h>      <stdlib.h>
    <float.h>   <signal.h>      <string.h>
    <limits.h>  <stdarg.h>      <time.h>


So, we can probably get rid of the AC_CHECK_HEADERS entries for errno.h
limits.h string.h and move from using varargs.h to using stdarg.h if that
is desirable.

        -- Mark

reply via email to

[Prev in Thread] Current Thread [Next in Thread]