All, I've been asked by Wendell to forward this query about C
interpreters to the mailing list for him.
----- Forwarded message from Wendell P <wendellp(a)operamail.com> -----
I have a project at softwarepreservation.org to collect work done,
mostly in the 1970s and 80s, on C interpreters.
http://www.softwarepreservation.org/projects/interactive_c
One thing I'm trying to track down is Cin, the C interpreter in UNIX
v10. I found the man page online and the tutorial in v2 of the Saunders
book, but that's it. Can anyone help me to find files or docs?
BTW, if you have anything related to the other commercial systems
listed, I'd like to hear. I've found that in nearly all cases, the
original developers did not keep the files or papers.
Cheers,
Wendell
----- End forwarded message -----
All, I was invited to give a talk at a symposium in Paris
on the early years of Unix. Slides and recording at:
http://minnie.tuhs.org/Z3/Hapop3/
Feel free to point out the inaccuracies :-)
For example, I thought Unix was used at some point
as the OS for some of the ESS switches in AT&T, but
now I think I was mistaken.
That's a temp URL, it will move somewhere else
eventually.
Cheers, Warren
On 2016-07-01 15:43, William Cheswick <ches(a)cheswick.com> wrote:
>
>>> >>...why didn't they have a more capable kernel than MS-DOS?
> >I don't think they cared. or felt it was needed at the time (I disagreed then and still do).
>
> MS-DOS was a better choice at the time than Unix. It had to fit on floppies, and was very simple.
>
> “Unix is a system administrations nightmare” — dmr
>
> Actually, MS-DOS was a runtime system, not an operating system, despite the last two letters of its name.
> This is a term of art lost to antiquity.
Strangely enough, the definition I have of a runtime system is very
different than yours. Languages had/have runtime systems. Some
environments had runtime systems, but they have a somewhat different
scope than what MS-DOS is.
I'd call MS-DOS a program loader and a file system.
> Run time systems offered a minimum of features: a loader, a file system, a crappy, built-in shell,
> I/O for keyboards, tape, screens, crude memory management, etc. No multiuser, no network stacks, no separate processes (mostly). DEC had several (RT11, RSTS, RSX) and the line is perhaps a little fuzzy: they were getting operating-ish.
Uh? RSX and RSTS/E are full fledged operating systems with multiuser
proteciton, time sharing, virtual memory, and all bells and whistles you
could ever ask for... Including networking... DECnet was born on RSX.
And RSTS/E offered several runtime systems, it had an RT-11 runtime
system, an RSX runtime system, you also had a TECO runtime system, and
the BASIC+ runtime system, and you could have others. You could
definitely have had a Unix runtime system in RSTS/E as well, but I don't
know if anyone ever wrote one.
In RSX, compilers/languages have runtime systems, which you linked with
your object files for that language, in order to get a complete runnable
binary.
Johnny
Ori Idan <ori(a)helicontech.co.il> asks today:
>> Pascal compiler written in Pascal? how can I compile the compiler it I
>> don't yet have a pascal compiler? :-)
You compile the code by hand into assembly language for the CDC
6400/6600 machines, and bootstrap that way: see
Urs Ammann
On Code Generation in a PASCAL Compiler
http://dx.doi.org/10.1002/spe.4380070311
Niklaus Wirth
The Design of a PASCAL Compiler
http://dx.doi.org/10.1002/spe.4380010403
It has been a long time since I read those articles in the journal
Software --- Practice and Experience, but my recollection is that they
wrote the compiler in a minimal subset of Pascal needed to do the job,
just to ease the hand-translation process.
-------------------------------------------------------------------------------
- Nelson H. F. Beebe Tel: +1 801 581 5254 -
- University of Utah FAX: +1 801 581 4148 -
- Department of Mathematics, 110 LCB Internet e-mail: beebe(a)math.utah.edu -
- 155 S 1400 E RM 233 beebe(a)acm.org beebe(a)computer.org -
- Salt Lake City, UT 84112-0090, USA URL: http://www.math.utah.edu/~beebe/ -
-------------------------------------------------------------------------------
On 2016-06-30 21:22, Clem Cole <clemc(a)ccc.com> wrote:
>
> but when Moto came out with a memory management chip it had some
>> > severe flaws that made paging and fault recovery impossible, while the
>> > equivalent features available on the 8086 line were tolerable.
> Different issues...
>
> When the 68000 came out there was a base/limit register chip available,
> who's number I forget (Moto offered to Apple for no additional cost if they
> would use it in the Mac but sadly they did not). This chip was similar
> to the 11/70 MMU, as that's what Les and Nick were used to using (they used
> a 11/70 running Unix V6 has the development box and had been before the
> what would become the 68000 -- another set of great stories from Les, Nick
> and Tom Gunter).
Clem, I think pretty much all you are writing is correct, except that I
don't get your reference to the PDP-11 MMU.
The MMU of the PDP-11 is not some base/limit register thing. It's a
paged memory, with a flat address space. Admittedly, you only have 8
pages, but I think it's just plain incorrect to call it something else.
(Even though noone I know of ever wrote a demand-paged memory system for
a PDP-11, there is no technical reason preventing you from doing it.
Just that with 8 pages, and load more physical memory than virtual, it
just didn't give much of any benifits.)
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
