>>>> "Zane" == Zane H Healy
<healyzh(a)aracnet.com> writes:
> On Thu, Oct 21, 2004 at 05:57:31PM -0700, Zane H.
Healy wrote: > I
> should have remembered DECUS C, I thought Watersmith (is that the
> right > name) or someone else might have had a version for RSTS/E
> as well.
>
> Whitesmith. We used the Whitesmith's C compiler for VMS
> extensively for data comm products at Software Results Corp... so
> extensively that we were also a 'reseller' to be able to provide
> it to our customers who ponied-up for a source license.
> Otherwise, they couldn't have recompiled our sources.
>
> Unfortunately for this thread, we used the DECUS C compiler for
> our RSTS products, not Whitesmith's, so I cannot offer any help in
> procuring anything for the PDP-11.
>
> -ethan
Zane> I dug up my doc's this morning. Looks like I should have
Zane> Whitesmith C and Pascal V2.2. It looks like they only
Zane> supported RSTS/E in RSX mode. Therefore the only options are
Zane> DEC C and DECUS C.
Huh?
It's possible to write applications that are "native RSTS" but I can't
think of any example where this has been done. Runtime systems use
native RSTS calls, but applications universally are either RT flavored
(using the RT11 runtime system to run on RSTS) or RSX flavored (using
the RSX runtime system or the kernel emulation in later RSTS
versions). Either way, an application might also include the
occasional RSTS native call, to do things that are outside the RT or
RSX API, but that would only be a small increment on top of an
otherwise RSX or RT application.
If someone says "support RSTS/E in RSX mode" that means the programs
run on the RSX runtime system on RSTS/E. If they say that much, it
might mean that they actually handled those few spots where an
unmodified plain RSX application behaves somewhat strangely in the
RSTS RSX emulation. (I don't remember actual examples of that; RT
emulation had some of these, but RT is more distant from RSTS in many
ways, for example its file structure.)
paul