Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!udel!rochester!rutgers!att!mcdchg!tellab5!nucsrl!accuvax.nwu.edu!casbah.acns.nwu.edu!eecs.nwu.edu!phil From: phil@eecs.nwu.edu (William LeFebvre) Newsgroups: comp.sys.encore Subject: Re: cpp symbol for multimax Message-ID: <240@casbah.acns.nwu.edu> Date: 3 Oct 90 15:48:20 GMT References: <26458@cs.yale.edu> <84281@tut.cis.ohio-state.edu> Sender: news@casbah.acns.nwu.edu Reply-To: phil@eecs.nwu.edu (William LeFebvre) Organization: EECS Department, Northwestern University Lines: 25 In article , aglew@crhc.uiuc.edu (Andy Glew) writes: |>(2) All of these symbols, sun, sequent, ns32032... |> should really have _s in front of their names, |> to avoid collisions with user variable names? |> |> (Ever have to port a program dealing with solar power?) I was quite surprised the first time I tried to compile the BSD sources for lpr/lpd on a Sun. Turns out that Berkeley declared the sockaddr_un structure (for the Unix domain socket) to be called "sun". Sigh. I've complained before that these names should be in all upper case or something (like maybe preceded with _), but no one ever listens to me. At this point, inertia is against us. I think I'll start a computer manufacturing company and call it "index", or maybe just "i". :-) William LeFebvre Computing Facilities Manager and Analyst Department of Electrical Engineering and Computer Science Northwestern University