Standards compliance test program Ver 0.0 
Author Message
 Standards compliance test program Ver 0.0

hello, world\n

this is a message to all those concerned about C Standard compliance on
both sides of the fence, that is, users and vendors.

 Users:   Now you have the chance to stand up and speak out. Complain
          to vendors about missing standards compliance. Bug them.
          Show you are taking their claims serious. Let them know you
          don't like being lied to. There's a contract that must be
          fulfilled. Together we can make a change. Unite!

 Vendors: Wouldn't it be nice to be able to point at other vendors and
          laugh at them because they can't get the most simple Standard
          Specifications right? Be the first to comply. Stay ahead in
          the competition. Become known for quality products.

Okay, enough hype. If you're still with me here you might find it
valuable and enlightening if you read the next few dozen lines and
take appropriate actions. And no, this is not about me or you making
money fast, I swear.

Regards,

    Jens -- The man with a mission :-)

--

SIGSIG -- signature too long (core dumped)

/*
 * isomac.c - check system headers for ISO 9899:1990 compliance
 *
 * This is a simple minded program that tries to find illegal macro
 * definitions in system header files. Illegal macro definitions are
 * those not from the implementation name space (i.e. not starting with
 * an underscore) or not matching any identifier mandated by The
 * Standard. Some common macro names are considered okay, e.g. all those
 * beginning with E (which may be defined in <errno.h>) or ending in
 * _MAX. See the arrays prefix[] and suffix[] below for details.
 *
 * In a compliant implementation no other macros can be defined, because
 * you could write strictly conforming programs that may fail to compile
 * due to syntax errors: suppose <stdio.h> defines PIPE_BUF, then the
 * conforming
 *
 * #include <assert.h>
 * #include <stdio.h>      <- or where the bogus macro is defined
 * #include <string.h>
 * #define STR(x) #x
 * #define XSTR(x) STR(x)
 * int main (void)
 * {
 *    int PIPE_BUF = 0;
 *    assert (strcmp ("PIPE_BUF", XSTR (PIPE_BUF)) == 0);
 *    return 0;
 * }
 *
 * is expected to compile and meet the assertion. If it does not, your
 * compiler compiles some other language than Standard C.
 *
 * REQUIREMENTS:
 *   This program calls gcc to get the list of defined macros. If you
 *   don't have gcc you're probably out of luck unless your compiler or
 *   preprocessor has something similar to gcc's -dM option. Tune
 *   PRINT_MACROS in this case. This program assumes headers are found
 *   under /usr/include and that there is a writable /tmp directory.
 *   Tune SYSTEM_INCLUDE and TMPFILE if your system differs.
 *
 * HOW TO COMPILE AND RUN:
 *   cc isomac.c -o isomac      # any ISO C compiler will do
 *   ./isomac                   # simply run isomac without args
 *
 * OUTPUT:
 *   Each header file name is printed, followed by illegal macro names
 *   and their definition. For the above example, you would see
 *   ...
 *   /usr/include/stdio.h
 *   #define PIPE_BUF 5120
 *   ...
 *   If your implementation does not yet incorporate Amendment 1 you
 *   will see messages about iso646.h, wctype.h and wchar.h not being
 *   found.
 *
 * WHAT TO DO NEXT:
 *   Look at the header file and verify that the macro is really visible
 *   when your compiler is in *strict* ANSI/ISO C mode. This is
 *   important! Gcc needs -ansi -pedantic, some other compilers use -Xa.
 *   Usually this will define the macro __STDC__. The vendor extensions
 *   should be wrapped in an #ifndef __STDC__ or something similar. Then
 *   compile and run the above program. If a syntax error occurs or the
 *   assertion fails complain to whoever is responsible for the header
 *   files (note that this may *not* be your compiler vendor, but rather
 *   your system vendor) and ask whether they claim ISO C conformance.
 *   Most will (should) blush :-) I explicitly encourage you to send
 *   them this source in your bug report.
 *
 *   If Amendment 1 headers are missing, bug your vendor for an upgrade.
 *
 * COPYING CONDITIONS:
 *   You can do everything you want with this source except pretend that
 *   you wrote it. Credit where credit is due. Fair enough, isn't it?
 *
 * AUTHOR:

 *   Corrections and suggestions welcome.
 *
 * DISCLAIMER:
 *   You get what you pay for. I won't pay for anything you get or will
 *   not get by using this program. Again, fair enough, isn't it?
 *
 */

#include <stdio.h>
#include <string.h>
#include <stdlib.h>

#define TMPFILE             "/tmp/macros"
#define SYSTEM_INCLUDE      "/usr/include"
#define HEADER_MAX          (sizeof SYSTEM_INCLUDE "/123456.h")
#define PRINT_MACROS        "gcc -E -dM -ansi -pedantic -I" SYSTEM_INCLUDE
#define COMMAND_MAX         256

/* ISO C header names including Amendment 1 (without ".h" suffix) */
static char *header[] = {
    "assert", "ctype", "errno", "float", "iso646", "limits", "locale",
    "math", "setjmp", "signal", "stdarg", "stddef", "stdio", "stdlib",
    "string", "time", "wchar", "wctype"

Quote:
};

/* Macros with these prefixes are considered okay */
static char *prefix[] = {
    "_", "E", "is", "str", "mem", "SIG", "FLT_", "DBL_", "LDBL_",
    "LC_", "wmem", "wcs"

Quote:
};

/*
 * Macros with these suffixes are considered okay.
 * Will not work for parameterized macros with arguments.
 */
static char *suffix[] = {
    "_MAX", "_MIN"

Quote:
};

/* These macros are considered okay. In fact, these are just more prefixes. */
static char *macros[] = {
    "BUFSIZ", "CHAR_BIT", "CHAR_MAX", "CHAR_MIN", "CLOCKS_PER_SEC",
    "DBL_DIG", "DBL_EPSILON", "DBL_MANT_DIG", "DBL_MAX",
    "DBL_MAX_10_EXP", "DBL_MAX_EXP", "DBL_MIN", "DBL_MIN_10_EXP",
    "DBL_MIN_EXP", "EDOM", "EILSEQ", "EOF", "ERANGE", "EXIT_FAILURE",
    "EXIT_SUCCESS", "FILENAME_MAX", "FLT_DIG", "FLT_EPSILON",
    "FLT_MANT_DIG", "FLT_MAX", "FLT_MAX_10_EXP", "FLT_MAX_EXP",
    "FLT_MIN", "FLT_MIN_10_EXP", "FLT_MIN_EXP", "FLT_RADIX",
    "FLT_ROUNDS", "FOPEN_MAX", "HUGE_VAL", "INT_MAX", "INT_MIN",
    "LC_ALL", "LC_COLLATE", "LC_CTYPE", "LC_MONETARY", "LC_NUMERIC",
    "LC_TIME", "LDBL_DIG", "LDBL_EPSILON", "LDBL_MANT_DIG", "LDBL_MAX",
    "LDBL_MAX_10_EXP", "LDBL_MAX_EXP", "LDBL_MIN", "LDBL_MIN_10_EXP",
    "LDBL_MIN_EXP", "LONG_MAX", "LONG_MIN", "L_tmpnam", "MB_CUR_MAX",
    "MB_LEN_MAX", "NDEBUG", "NULL", "RAND_MAX", "SCHAR_MAX",
    "SCHAR_MIN", "SEEK_CUR", "SEEK_END", "SEEK_SET", "SHRT_MAX",
    "SHRT_MIN", "SIGABRT", "SIGFPE", "SIGILL", "SIGINT", "SIGSEGV",
    "SIGTERM", "SIG_DFL", "SIG_ERR", "SIG_IGN", "TMP_MAX", "UCHAR_MAX",
    "UINT_MAX", "ULONG_MAX", "USHRT_MAX", "WCHAR_MAX", "WCHAR_MIN",
    "WEOF", "_IOFBF", "_IOLBF", "_IONBF", "abort", "abs", "acos",
    "acosf", "acosl", "and", "and_eq", "asctime", "asin", "asinf",
    "asinl", "assert", "atan", "atan2", "atan2f", "atan2l", "atanf",
    "atanl", "atexit", "atof", "atoi", "atol", "bitand", "bitor",
    "bsearch", "btowc", "calloc", "ceil", "ceilf", "ceill", "clearerr",
    "clock", "clock_t", "compl", "cos", "cosf", "cosh", "coshf",
    "coshl", "cosl", "ctime", "difftime", "div", "div_t", "errno",
    "exit", "exp", "expf", "expl", "fabs", "fabsf", "fabsl", "fclose",
    "feof", "ferror", "fflush", "fgetc", "fgetpos", "fgets", "fgetwc",
    "fgetws", "floor", "floorf", "floorl", "fmod", "fmodf", "fmodl",
    "fopen", "fprintf", "fputc", "fputs", "fputwc", "fputws", "fread",
    "free", "freopen", "frexp", "frexpf", "frexpl", "fscanf", "fseek",
    "fsetpos", "ftell", "fwide", "fwprintf", "fwrite", "fwscanf",
    "getc", "getchar", "getenv", "gets", "getwc", "getwchar", "gmtime",
    "isalnum", "isalpha", "iscntrl", "isdigit", "isgraph", "islower",
    "isprint", "ispunct", "isspace", "isupper", "iswalnum", "iswalpha",
    "iswcntrl", "iswctype", "iswdigit", "iswgraph", "iswlower",
    "iswprint", "iswpunct", "iswspace", "iswupper", "iswxdigit",
    "isxdigit", "labs", "ldexp", "ldexpf", "ldexpl", "ldiv", "ldiv_t",
    "localeconv", "localtime", "log", "log10", "log10f", "log10l",
    "logf", "logl", "longjmp", "malloc", "mblen", "mbrlen", "mbrtowc",
    "mbsinit", "mbsrtowcs", "mbstate_t", "mbstowcs", "mbtowc", "memchr",
    "memcmp", "memcpy", "memmove", "memset", "mktime", "modf", "modff",
    "modfl", "not", "not_eq", "offsetof", "or", "or_eq", "perror",
    "pow", "powf", "powl", "printf", "ptrdiff_t", "putc", "putchar",
    "puts", "putwc", "putwchar", "qsort", "raise", "rand", "realloc",
    "remove", "rename", "rewind", "scanf", "setbuf", "setjmp",
    "setlocale", "setvbuf", "sig_atomic_t", "signal", "sin", "sinf",
    "sinh", "sinhf", "sinhl", "sinl", "size_t", "sprintf", "sqrt",
    "sqrtf", "sqrtl", "srand", "sscanf", "stderr", "stdin", "stdout",
    "strcat", "strchr", "strcmp", "strcoll", "strcpy", "strcspn",
    "strerror", "strftime", "strlen", "strncat", "strncmp", "strncpy",
    "strpbrk", "strrchr", "strspn", "strstr", "strtod", "strtok",
    "strtol", "strtoul", "strxfrm", "swprintf", "swscanf", "system",
    "tan", "tanf", "tanh", "tanhf", "tanhl", "tanl", "time", "time_t",
    "tmpfile", "tmpnam", "tolower", "toupper", "towctrans", "towlower",
    "towupper", "ungetc", "ungetwc", "va_arg", "va_end", "va_start",
    "vfprintf", "vfwprintf", "vprintf", "vsprintf", "vswprintf",
    "vwprintf", "wchar_t", "wcrtomb", "wcscat", "wcschr", "wcscmp",
    "wcscoll", "wcscpy", "wcscspn", "wcsftime", "wcslen", "wcsncat",
    "wcsncmp", "wcsncpy", "wcspbrk", "wcsrchr", "wcsrtombs", "wcsspn",
    "wcsstr", "wcstod", "wcstok", "wcstol", "wcstombs", "wcstoul",
    "wcsxfrm", "wctob", "wctomb", "wctrans", "wctrans_t", "wctype",
    "wctype_t", "wint_t", "wmemchr", "wmemcmp", "wmemcpy", "wmemmove",
    "wmemset", "wprintf", "wscanf", "xor", "xor_eq"

Quote:
};

#define NUMBER_OF_HEADERS              (sizeof header/sizeof *header)
#define NUMBER_OF_PREFIXES             (sizeof prefix/sizeof *prefix)
#define NUMBER_OF_SUFFIXES      
...

read more »



Fri, 21 May 1999 03:00:00 GMT  
 Standards compliance test program Ver 0.0

Quote:

> this is a message to all those concerned about C Standard compliance on
> both sides of the fence, that is, users and vendors.

Well, I have too...

Quote:
>  Vendors: Wouldn't it be nice to be able to point at other vendors and
>           laugh at them because they can't get the most simple Standard
>           Specifications right? Be the first to comply. Stay ahead in
>           the competition. Become known for quality products.

> Okay, enough hype. If you're still with me here you might find it
> valuable and enlightening if you read the next few dozen lines and
> take appropriate actions. And no, this is not about me or you making
> money fast, I swear.

In case somebody is interested: with the GNU libc-2.0 (which I
maintain) I get on Linux:


/usr/include/assert.h
/usr/include/ctype.h
/usr/include/errno.h
/usr/include/float.h
/usr/include/iso646.h
/usr/include/limits.h
/usr/include/locale.h
/usr/include/math.h
/usr/include/setjmp.h
/usr/include/signal.h
/usr/include/stdarg.h
/usr/include/stddef.h
/usr/include/stdio.h
/usr/include/stdlib.h
/usr/include/string.h
/usr/include/time.h
/usr/include/wchar.h
/usr/include/wctype.h

The only problem was that the files float.h, iso646.h, stdarg.h, and
stddef.h are not in /usr/include but in the gcc specific directory.
The test program could perhaps be changed to know this.  As an
argument it could get a list of directories to look in for the
headers.

--
-- Uli

Ulrich Drepper  \    ,-------------------'   \  76149 Karlsruhe/Germany



Sat, 29 May 1999 03:00:00 GMT  
 
 [ 2 post ] 

 Relevant Pages 

1. Casting problem or Formatiing side effect - diff between 0/0 - 0.0/0.0

2. Annonce: `` v '', the Non Standard C Library (version 0.0)

3. VC++ 7.0 compliance with C++ standard

4. Standards compliance

5. Y2K compliance of C standard time_t routines

6. Y2k Compliance vs ANSI standard

7. compliance with the standard?

8. standards compliance in VC++ 7

9. Standards compliance and VC++ 6.0

10. vc6 standard compliance

11. VC++ standards compliance

12. VC++ 7.0 Standard Compliance - Templates / Intel Compiler

 

 
Powered by phpBB® Forum Software