Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Sep 2002 00:07:00 -0700
From:      "David O'Brien" <obrien@FreeBSD.org>
To:        Garrett Wollman <wollman@lcs.mit.edu>
Cc:        current@FreeBSD.org, kan@FreeBSD.org
Subject:   Re: No way to tell when `long long' is or is not supported?
Message-ID:  <20020909070700.GA26978@dragon.nuxi.com>
In-Reply-To: <200209090350.g893oHMs062192@khavrinen.lcs.mit.edu>
References:  <200209090350.g893oHMs062192@khavrinen.lcs.mit.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 08, 2002 at 11:50:17PM -0400, Garrett Wollman wrote:
> GCC used to define a macro __STRICT_ANSI__ when `-ansi' was given on
> the command line.  The current version does not do this,

It seems to work for me:

    $ cat foo.c
    #ifdef __STRICT_ANSI__
    #error __STRICT_ANSI__
    #endif
    $ /usr/bin/cc -ansi foo.c
    foo.c:2:2: #error __STRICT_ANSI__

The problem is it is also set for this:

    $ /usr/bin/cc -std=c99 foo.c
    foo.c:2:2: #error __STRICT_ANSI__

As you mentioned, this is now not a good test to decide if 'long long' is
supported.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020909070700.GA26978>