Re: code portability
- From: Al Balmer <albalmer@xxxxxxx>
- Date: Wed, 02 Aug 2006 21:26:55 GMT
On Wed, 02 Aug 2006 21:00:26 +0200, jacob navia
<jacob@xxxxxxxxxxxxxxxx> wrote:
Al Balmer wrote:
On Wed, 02 Aug 2006 09:49:08 +0200, jacob navia
<jacob@xxxxxxxxxxxxxxxx> wrote:
Tom St Denis a écrit :
Eigenvector wrote:
What about the programmers who submit to the archives? That is mainly where
I see massive gcc and imake requirements. In fact I have on occassion
attempted to compile applications - such as gcc using my native Intel or xlC
compilers without luck. Again this isn't a question on how to compile GCC,
but rather is the experience that the OpenSource community tries to conform
to ANSI standards?
GCC is hardly your average OSS project (and Intel C is hardly standard
conforming).
You are just speaking nonsense. As specified here:
http://www.intel.com/cd/ids/developer/asmo-na/eng/dc/tools/compilers/236372.htm?page=4
the intel compiler complies with C99.
It doesn't say that at all. Did you actually read the article?
You can't read?
In that page the option
-std=c99
is mentioned with explanation:
" C99 conformance and feature support"
And that's what you're basing your conclusion on? An entry in a
options table? The name of one of the C++ options is "_strict_ansi",
but in the text above, they tell you that the C++ compiler has only "a
high degree of conformance." IOW, it's not "strict ansi."
As one who claims to be a compiler vendor, you should know that
standards compliance should be supplied as a separate statement, along
with the required statement of implementation dependent behavior.
It's entirely possible that Intel is fully C99 compliant (though you'd
think they would say so in their ads), but you can't tell from the
page you gave us.
in the first table of that page.
And you say:
It doesn't say that at all. Did you actually read the article?
There is no blinder person as the one that doesn't want to see!
jacob
--
Al Balmer
Sun City, AZ
.
- References:
- code portability
- From: Eigenvector
- Re: code portability
- From: Tom St Denis
- Re: code portability
- From: Eigenvector
- Re: code portability
- From: Tom St Denis
- Re: code portability
- From: jacob navia
- Re: code portability
- From: Al Balmer
- Re: code portability
- From: jacob navia
- code portability
- Prev by Date: writing to a text file line by line
- Next by Date: Re: code portability
- Previous by thread: Re: code portability
- Next by thread: Re: code portability
- Index(es):
Relevant Pages
|