home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.arch
- Path: sparky!uunet!walter!gizmo!mo
- From: mo@gizmo.bellcore.com (Michael O'Dell)
- Subject: Re: reentrant, etc...
- Message-ID: <1993Jan2.220400.28309@walter.bellcore.com>
- Keywords:
-
- Sender: news@walter.bellcore.com
- Nntp-Posting-Host: gizmo.bellcore.com
- Reply-To: mo@bellcore.com
- Organization: Center for Chaotic Repeatabilty
- References: <C04zn2.A95.2@cs.cmu.edu> <1993Jan2.122544.26198@sei.cmu.edu> <C08qF4.Knz@news.iastate.edu>
- Date: Sat, 2 Jan 93 22:04:00 GMT
- Lines: 22
-
- OS/360 MFT & MVT back in the late 60s/early 70s had full support for
- threads, and distinguished between reentrant and serially-reusable modules
- (not to mention fully async I/O and many other things, some good). And of
- course, OS/360 wasn't the first commercial operating system to support
- such notions (Burroughs MCP on the 5500 may come close to the first,
- though).
-
- As for "horrid", a better description is "misunderstood" or "well
- disguised". The fact that all the facilities were available only
- to ASM programmers did much to conceal the horsepower there.
- There were certainly things the OS/360 didn't do very well, but they
- didn't lack for richness. Actually, that was the greatest weakness:
- OS/360 had everything in the world EXCEPT a simple way to do something.
-
- "All mechanism but no policy."
-
- Does this sound familiar?
-
- -Mike
-
- Bellcore?? Bellcore isn't allowed to hold opinions. Any here were
- found along the road somewhere down through the ages.
-