Article View: vmsnet.alpha
Article #19Re: Should /standard=xxxx affect link behavior?
From: Pat Rankin
Date: Tue, 15 Dec 1992 01:53
Date: Tue, 15 Dec 1992 01:53
21 lines
1534 bytes
1534 bytes
In article <4052@mitech.com>, gjc@mitech.com (George J. Carrette) writes...
> Here is an interesting one, compiling a file with
> the setting /STANDARD=RELAXED_ANSI89 vs /STANDARD=portable
> has an effect on how the linker sees external references
> the the DECC$SHR.EXE
No, not really. It has an effect on whether or not the compiler
automatically attaches the "decc$" prefix to the external name. Of course
that does indirectly affect linker behavior.
> %LINK-I-UDFSYM, TIMES
times() is not an ANSI standard function, so the compiler can not
usurp external identifier `times' from the user's namespace when it's
operating in ANSI mode. DEC C is doing exactly the right thing here.
If you look through <time.h>, you'll see a comment telling you to use
/undefine="__HIDE_FORBIDDEN_NAMES" when compiling. In the one I'm looking
at it says that that's needed for strict ANSI mode rather than relaxed.
It should apply to any mode which purports to be standard conforming.
Pat Rankin, rankin@eql.caltech.edu
Technical Details
Message-ID:
<14DEC199218530277@eql.caltech.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!nntp-server.caltech.edu!eql.caltech.edu!rankinReferences:
<4052@mitech.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!nntp-server.caltech.edu!eql.caltech.edu!rankin From: rankin@eql.caltech.edu (Pat Rankin) Newsgroups: vmsnet.alpha Subject: Re: Should /standard=xxxx affect link behavior? Date: 14 Dec 1992 18:53 PDT Organization: California Institute of Technology Lines: 21 Distribution: world Message-ID: <14DEC199218530277@eql.caltech.edu> References: <4052@mitech.com> NNTP-Posting-Host: eql.caltech.edu News-Software: VAX/VMS VNEWS 1.41