Re: Linking Problem

> I haven't tried this with Unix,

You do need to ensure that external names are in the correct format for
the OS being run on, but all my file names, for example, are held in a
system control file so that this is never a problem for me.

Also there are different routines supplied with different run-times so
there are many thinks which could stop .int s from being portable; or
actuall stop source code from creating portable applications.

> even without INTLEVEL.

The defaul seems to be INTLEVEL"2" which is probably maximum
portability.

.

Relevant Pages

  • Re: Linking Problem
    ... >> I haven't tried this with Unix, ... > You do need to ensure that external names are in the correct format for ... > system control file so that this is never a problem for me. ... > portability. ...
    (comp.lang.cobol)
  • Re: Garbage Collection - Stop Making Trash
    ... Try moving Unix headers to Windows, ... attempt to sabotage portability -- we achieve limited portability ... except that no standards committee has endorsed an interface ... Microsoft loves this mentality. ...
    (comp.lang.cpp)
  • Re: Standard Ada Preprocessor
    ... Portability of course is an important issue. ... How would you compile a Unix program ... perceived "standard" language, I think. ...
    (comp.lang.ada)
  • Re: OT] Joerg Schilling flames Linux on his Blog
    ... Portability is relative. ... It's normally handled with a wrapper. ... time to write than a Unix wrapper which would provide the ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: About extensible prinf(3), a slightly long X-mas card
    ... >>>Perhaps the semantics of this extended printf() are so far divorced from the ... Everything under the sun has a portability cost these days because ... the portable subset of the UNIX API is still too small to support ...
    (freebsd-current)