Re: [POSIX & Win32API] Getting the 'routing' informations

Golden California Girls <gldncagrls@xxxxxxxxxxx> writes:
CBFalconer wrote:
No, only ISO defines a version of C that can port anywhere. All it
needs is a conforming C compiler, and what it must conform to is
carefully spelled out. Other manufacturers/people/organizations can
prepare systems with various extensions, but once code is written to
use those extensions it no longer ports to any compliant system.

You seem to totally miss the fact that here, on clc, the objective
is portable software, using components that are known to all.

Replace ISO with GNU and you have an equally true proposition.
[...]

The GNU folks themselves don't refer to their dialect of C as a
standard. See, for example, this excerpt from gcc's documentation:

Extensions to the C Language Family
***********************************

GNU C provides several language features not found in ISO
standard C. (The `-pedantic' option directs GCC to print a
warning message if any of these features is used.) To test for
the availability of these features in conditional compilation,
check for a predefined macro `__GNUC__', which is always defined
under GCC.

These extensions are available in C and Objective-C. Most of
them are also available in C++. *Note Extensions to the C++
Language: C++ Extensions, for extensions that apply _only_ to C++.

Some features that are in ISO C99 but not C89 or C++ are also,
as extensions, accepted by GCC in C89 mode and in C++.

The ISO standard defines the language; GNU C is defined in
relationship to that standard.

--
Keith Thompson (The_Other_Keith) kst-u@xxxxxxx <http://www.ghoti.net/~kst>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"
.

Relevant Pages

  • Re: Fortran Features
    ... without a specific list of extensions. ... In order to make the features optional like this, ... will need to be included in the standard. ... means that you get into a substantial debate on each ...
    (comp.lang.fortran)
  • Re: Does a C89 compliant compiler exist?
    ... >> In my previous post I mentioned I'm trying to test the portability of my ... > Determine the language standard. ... This option basically disables the GNU C features that conflict with the ...
    (comp.lang.c)
  • Re: idea: on the issue of C and language extensions
    ... features; this route would be based mostly on something like a mailing ... implementations, yet far lighter weight and informal than forcing ... extensions they have done already... ... When parts of the Standard released by such a major organisation like ...
    (comp.std.c)
  • Re: J3s workings
    ... If those features are adopted by several compilers, ... But how can we test out new features before standardizing them? ... I've no big problem with extensions for this purpose. ... be a big problem if the standard is different. ...
    (comp.lang.fortran)
  • Re: idea: on the issue of C and language extensions
    ... features; this route would be based mostly on something like a mailing ... The key problem would be in reaching an agreement on these extensions. ... When parts of the Standard released by such a major organisation like ... useful domain-specific and experimental implementations). ...
    (comp.std.c)