decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
I was going to say the same thing | 451 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
I was going to say the same thing
Authored by: bprice on Friday, May 04 2012 @ 07:39 PM EDT
(Grolegians should know by now that when someone mentions one of my magic words, like B6700, I will awaken.)
From Memory: B6700Algol is 'Algol 68'.
Take it from the guy that wrote major portions of the compiler as well as the BNF syntax as found in the manual you learned form: your memory is not correct. The B6700 Extended Algol language was based on Algol 60, not Algol 58 (that was called BALGOL, for the Burroughs 220), nor Algol 68 (which was too late for the the B6700).

The Algol 60 language, like FORTRAN and COBOL, its contemporaries, did not have APIs. The math functions were built in (intrinsic to) the core language, and it was the compiler's job to generate what's now called ABI code, for any such items that were support-library features. Our compilers tended to handle simple stuff, like ABS, in line, except as an actual parameter of type REAL PROCEDURE(REAL value).

Effective with the MCP Mark II, io was handled by our homebrew object-oriented file-access system. The compiler generated a file-object token for each file, and the OS filled in method tokens for the appropriate methods, depending on attributes of the file, and its state and use history within the program. The compiler generated method-call code in the ABI for each io statement in the program.

---
--Bill. NAL: question the answers, especially mine.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )