Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!bin
From: bin@primate.wisc.edu (Brain in Neutral)
Newsgroups: comp.sys.mips
Subject: Re: R4 server for RS1210 (aka NCD16)?
Message-ID: <3202@uakari.primate.wisc.edu>
Date: 1 Oct 90 15:48:32 GMT
References: <41823@mips.mips.COM>
Sender: bin@primate.wisc.edu
Reply-To: bin@primate.wisc.edu
Lines: 28

I should clarify two points from my previous posting:

(1) I don't know if "RISCOS" is indeed unique or not.  However, it is
connotatively very ambiguous since there are two OS's with RISC and OS
in the name.
(2) I hope that my tone did not imply anger at MIPS.  But I have been
frustrated (quite) by the lack of a good symbol for describing true MIPS
systems when building projects using imake.

From article <41823@mips.mips.COM>, by rogerk@mips.COM (Roger B.A. Klorese):
> In article <3201@uakari.primate.wisc.edu> bin@primate.wisc.edu writes:
>>> We use RISCOS.
>>ARGHH, NOOO!!  This is not unique.  Heard of Acorn Systems in the UK?
>>	riscos	(on RISC OS systems)
> 
> Yes, but cpp is case-sensitive.  When we have an ANSI C compiler, we will
> use symbols consistent with ANSI.  For now, use RISCOS for Mips, and if
> you wish to, riscos for ARM.

Case-sensitive, true, but still confusing.  As a symbol, RISCOS signifies
nothing about the company/product line to which it applies.  It's better
than nothing, perhaps, but I wouldn't say RISCOS qualifies as a good symbol.
Oh, well.
--
Paul DuBois
dubois@primate.wisc.edu

                 "Was all of this because I wore a big man's hat?"