code portability

My question is more generic, but it involves what I consider ANSI standard C
and portability.

I happen to be a system admin for multiple platforms and as such a lot of
the applications that my users request are a part of the OpenSource
community. Many if not most of those applications strongly require the
presence of the GNU compiling suite to work properly. My assumption is that
this is due to the author/s creating the applications with the GNU suite.
Many of the tools requested/required are GNU replacements for make,
configure, the loader, and lastly the C compiler itself. Where I'm going
with this is, has the OpenSource community as a whole committed itself to at
the very least encouraging its contributing members to conform to ANSI
standards of programming?

My concern is that as an admin I am sometimes compelled to port these
applications to multiple platforms running the same OS and as the user
community becomes more and more insistent on OpenSource applications will
gotcha's appear due to lack of portability in coding? I fully realize that
independent developers may or may not conform to standards, but again is it
at least encouraged?

11.32 of the FAQ seemed to at least outline the crux of what I am asking.
If I loaded up my home machine to the gills will all open source compiler
applications (gcc, imake, autoconfig, etc....) would my applications that I
compile and link and load conform?


.

Relevant Pages

  • Re: code portability
    ... the applications that my users request are a part of the OpenSource ... GCC attempts to conform to C90 and C99 and in many regards it's there. ... independent developers may or may not conform to standards, ... If I loaded up my home machine to the gills will all open source compiler ...
    (comp.lang.c)
  • Re: C# syntax as an option in Delphi w32
    ... monitor the Objects lifecycle. ... Each native executable has it's own heap manager, ... which are the main reason why a C++ compiler has to ... faster than heap allocations in native applications and you the GC heap ...
    (borland.public.delphi.non-technical)
  • Re: wuts so good about sp2??
    ... > written correctly for XP SP2 standards. ... > Everything has changed about computers for the SOHO user, ... > with newer applications and use the basic methods to compute (word ...
    (microsoft.public.windowsxp.general)
  • Re: code portability
    ... the applications that my users request are a part of the OpenSource ... GCC attempts to conform to C90 and C99 and in many regards it's there. ... Again this isn't a question on how to compile GCC, ... to ANSI standards? ...
    (comp.lang.c)
  • Re: What micros do you actually hate to work with?
    ... I have hear the Microchip compiler is not the tightest, ... The PIC16 reports in Words, the PIC18 in bytes, but that still puts you at 3 times bigger. ... I find that the type of code where the choice of assembly or C makes the most difference is for small but complete applications. ... Had Jon said he went from 20k assembly to 120k C, I'd be a lot more sceptical. ...
    (comp.arch.embedded)