Re: And speaking of ALGOL

2015-08-13 Thread Nigel Williams
> On 13 Aug 2015, at 4:41 am, Paul Koning wrote: > I found this out when I tried to write a program that reads foreign format > tapes, in particular past tape marks. Algol can’t do that — either that, or > the consultants couldn’t figure out how. I’m assuming the sentence above is in the same

Re: B 5000, MCP, etc - was Re: And speaking of ALGOL

2015-08-13 Thread Nigel Williams
> On 13 Aug 2015, at 1:04 pm, Toby Thain wrote: > For more on this, see "Classic Operating Systems," Per Brinch Hansen, which > reprints the paper "Operating System for the B 5000", Clark Oliphint (1964). > > "Two of the major B 5000 design objectives were (1) that all programming was > to be

Re: And speaking of ALGOL

2015-08-12 Thread Sean Caron
Ooh, thanks for that; I have long been intrigued by Burroughs ... they always tried rather unusual approaches ... seeing if I can get MCP fired up sounds like a fun weekend project. Best, Sean On Wed, Aug 12, 2015 at 3:28 PM, Jay Jaeger wrote: > In addition, B5500/B5700 Mark XIII and B5500/B5

B 5000, MCP, etc - was Re: And speaking of ALGOL

2015-08-12 Thread Toby Thain
On 2015-08-12 1:39 PM, Nigel Williams wrote: On 12 Aug 2015, at 11:24 pm, Paul Koning wrote: On Aug 11, 2015, at 10:23 PM, Mark Kahrs wrote: For those of you who might be interested, I sent a listing of the B6700 ALGOL compiler source code to the CHM. I did find a copy of the B6500 ESPOL

Re: And speaking of ALGOL

2015-08-12 Thread Jay Jaeger
In addition, B5500/B5700 Mark XIII and B5500/B5700 MARK XV.3 release tapes can be found online. UNISYS released these under the "UNISYS MCP MARK XIII SOFTWARE EDUCATIONAL/HOBBYIST LICENSE AGREEMENT" in 2012, having been approached by the owner of the tapes. At least Mark XIII is available on Paul

Re: And speaking of ALGOL

2015-08-12 Thread Paul Koning
> On Aug 12, 2015, at 1:39 PM, Nigel Williams > wrote: > > >> On 12 Aug 2015, at 11:24 pm, Paul Koning wrote: >> ... >> Did Algol come after the hardware? I always thought of the hardware as >> having been customized for their Algol, but admittedly I don’t actually know >> which is chicken

Re: And speaking of ALGOL

2015-08-12 Thread Nigel Williams
> On 12 Aug 2015, at 11:24 pm, Paul Koning wrote: >> On Aug 11, 2015, at 10:23 PM, Mark Kahrs wrote: >> For those of you who might be interested, I sent a listing of the B6700 >> ALGOL compiler source code to the CHM. > I did find a copy of the B6500 ESPOL compiler online recently. In the B55

Re: And speaking of ALGOL

2015-08-12 Thread Paul Koning
> On Aug 11, 2015, at 10:23 PM, Mark Kahrs wrote: > > I assure you Chuck, I do know the original B5500 ALGOL having written my > first program on one. > > For those of you who might be interested, I sent a listing of the B6700 > ALGOL compiler source code to the CHM. Did it end up online somew

Re: And speaking of ALGOL

2015-08-11 Thread Chuck Guzis
On 08/11/2015 07:23 PM, Mark Kahrs wrote: I assure you Chuck, I do know the original B5500 ALGOL having written my first program on one. For those of you who might be interested, I sent a listing of the B6700 ALGOL compiler source code to the CHM. I'm surprised no one has mentioned the Burrough

Re: And speaking of ALGOL

2015-08-11 Thread Mark Kahrs
I assure you Chuck, I do know the original B5500 ALGOL having written my first program on one. For those of you who might be interested, I sent a listing of the B6700 ALGOL compiler source code to the CHM. I'm surprised no one has mentioned the Burroughs extensions to ALGOL to optimise|ize the us

Re: And speaking of ALGOL

2015-08-11 Thread ben
On 8/11/2015 3:13 PM, Noel Chiappa wrote: > From: Paul Koning > Every machine needs a fast memory system. CISC machines just as much, > after all the number of memory references per operation of a given kind > doesn't depend on the sort of CPU architecture you use. You're fo

Re: And speaking of ALGOL

2015-08-11 Thread Noel Chiappa
> From: Paul Koning > Every machine needs a fast memory system. CISC machines just as much, > after all the number of memory references per operation of a given kind > doesn't depend on the sort of CPU architecture you use. You're forgetting the memory bandwidth for the instructio

Re: And speaking of ALGOL

2015-08-11 Thread ben
On 8/11/2015 9:37 AM, Paul Koning wrote: Which makes sense; it demonstrates what nearly everyone now knows, which is that RISC architecture is a very good way to design a computer. *NO* (Not with a single memory bus, that is) Have gun ... will travel. -:) Ben.

Re: And speaking of ALGOL

2015-08-11 Thread Paul Koning
> On Aug 11, 2015, at 12:20 PM, Chuck Guzis wrote: > > ... >> I suspect part of the reason is that Algol wasn’t all that popular in >> the USA even if its heyday. Add to that the fact that most computer >> designers weren’t all that skilled in software. And finally, as the >> RISC experience has

Re: And speaking of ALGOL

2015-08-11 Thread Chuck Guzis
On 08/11/2015 08:37 AM, Paul Koning wrote: No, it was a CDC product, but developed by CDC Holland (at their Rijswijk office). Apparently it was created at the insistence of a number of CDC’s academic customers in Europe. Which explains why I never saw it at CPD SVLOPS. CDC in those days was

Re: And speaking of ALGOL

2015-08-11 Thread Paul Koning
> On Aug 11, 2015, at 11:24 AM, Chuck Guzis wrote: > > On 08/11/2015 07:52 AM, Paul Koning wrote: > >> Yes, that was a pretty nice system. Certainly not the first ALGOL >> system, but a decent one even though they did put a bunch of >> Fortran-like ugliness into the I/O. > > As I recall, the

Re: And speaking of ALGOL

2015-08-11 Thread Chuck Guzis
On 08/11/2015 07:52 AM, Paul Koning wrote: Yes, that was a pretty nice system. Certainly not the first ALGOL system, but a decent one even though they did put a bunch of Fortran-like ugliness into the I/O. As I recall, the I/O in the Algol-60 report was not particularly well-defined. Pascal

Re: And speaking of ALGOL

2015-08-11 Thread Paul Koning
> On Aug 11, 2015, at 1:16 AM, Chuck Guzis wrote: > > On 08/10/2015 07:07 PM, Mark Kahrs wrote: >> One could always implement a KDF9 emulator and then port Randall and >> Russell code (from the book). >> >> And r.e. ALGOL68, Peter Hibbard had some sort of ALGOL68 system >> working on the PDP11s

Re: And speaking of ALGOL

2015-08-11 Thread Noel Chiappa
> From: Chuck Guzis > Why all this DEC stuff about Algol? I probably started it; I just mentioned the PDP-11 one because a lot of people already have either 11's, or an emulator up and running. Noel

Re: And speaking of ALGOL

2015-08-11 Thread Nigel Williams
On 11 Aug 2015, at 3:05 pm, Nigel Williams wrote: > > On Tue, Aug 11, 2015 at 12:07 PM, Mark Kahrs wrote: >> One could always implement a KDF9 emulator and then port Randall and >> Russell code (from the book). > > Both of those requirements are already done: > > http://www.findlayw.plus.com/

Re: And speaking of ALGOL

2015-08-10 Thread Chuck Guzis
On 08/10/2015 07:07 PM, Mark Kahrs wrote: One could always implement a KDF9 emulator and then port Randall and Russell code (from the book). And r.e. ALGOL68, Peter Hibbard had some sort of ALGOL68 system working on the PDP11s at CMU I believe. Why all this DEC stuff about Algol? Go to the so

Re: And speaking of ALGOL

2015-08-10 Thread Guy Sotomayor
On 8/10/15 7:07 PM, Mark Kahrs wrote: One could always implement a KDF9 emulator and then port Randall and Russell code (from the book). And r.e. ALGOL68, Peter Hibbard had some sort of ALGOL68 system working on the PDP11s at CMU I believe. It was a cross compiler. The compiler ran on TOP-10

Re: And speaking of ALGOL

2015-08-10 Thread Nigel Williams
On Tue, Aug 11, 2015 at 12:07 PM, Mark Kahrs wrote: > One could always implement a KDF9 emulator and then port Randall and > Russell code (from the book). Both of those requirements are already done: http://www.findlayw.plus.com/KDF9/emulation/emulator.html