🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: vmsnet.alpha
Article #21

Re: Should /standard=xxxx affect link behavior?

#21
From: George J. Carrette
Date: Tue, 15 Dec 1992 13:14
27 lines
1587 bytes
In article <14DEC199218530277@eql.caltech.edu>, rankin@eql.caltech.edu (Pat Rankin) writes:
>      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

Mine says that too. But it turned out I also needed 
/PREFIX_LIBRARY_ENTRIES=ALL_ENTRIES

Sorting out all these compiler switches. Argh!

Really, my problem is that I didn't sit down and study this stuff.
I just let some guy at the DEC porting center "do it for me."
Obviously disadvantages to that.

For example, all of a sudden with the new C compiler (X1.3)
lots of things work that I was having trouble with before.

I'm stilling trying to track down how some of my files
seem to have NOMEMBER_ALIGNMENT turned on without my knowing it.

-gjc
Technical Details
Message-ID: <4069@mitech.com>
Path: arc1-ca.pugleaf.net!sparky!uunet!mitech!gjc
References: <4052@mitech.com> <14DEC199218530277@eql.caltech.edu>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!mitech!gjc
From: gjc@mitech.com (George J. Carrette)
Newsgroups: vmsnet.alpha
Subject: Re: Should /standard=xxxx affect link behavior?
Message-ID: <4069@mitech.com>
Date: 15 Dec 92 13:14:12 GMT
References: <4052@mitech.com> <14DEC199218530277@eql.caltech.edu>
Distribution: world
Organization: Mitech Corporation, Concord MA
Lines: 27