Subject: Re: How about Not prepending underscores to variable nam
To: None <port-pmax@NetBSD.ORG>
From: Ralph Campbell <email@example.com>
Date: 09/16/1994 10:21:47
> From owner-port-pmax@NetBSD.ORG Thu Sep 15 21:15:20 1994
> Message-Id: <199409160358.UAA06204@sun-lamp.cs.berkeley.edu>
> X-Authentication-Warning: sun-lamp.cs.berkeley.edu: Host LOCALHOST didn't use HELO protocol
> To: Jonathan Stone <firstname.lastname@example.org>
> Cc: port-pmax@NetBSD.ORG
> Subject: Re: How about Not prepending underscores to variable names?
> In-Reply-To: Your message of "Thu, 15 Sep 1994 19:34:38 PDT."
> Date: Thu, 15 Sep 1994 20:58:24 -0700
> From: Adam Glass <glass@NetBSD.ORG>
> Sender: owner-port-pmax@NetBSD.ORG
> Precedence: list
> > The existing pmax code (such as locore.s) appears to be written to
> > follow the MIPS toolset convention, which is for the C compiler to not
> > prepend an underscore. From looking at GCC configuration files,
> > 4.4SBD seems to follow the same convention as the mips toolset.
> We are not bound by the behavior of the mips toolset.
I used the ULTRIX (MIPS co. based) compiler to bootstrap things so
following the no underscore convention was the easiest thing to do
initially. It does run into a few difficulties like nlist() and some
name conflicts like programs which use the global variable "start", etc.
At this point, NetBSD might reasonably consider switching although I
haven't found the differences all that much of a problem. I would say
it is more esthetic.