So SAFE in NEWP identifies parts of code that are in assembly language?
In C the term usually indicates improper use of pointer variables. Thiat language is very generous in offering options with unexpected side effects when using pointers.
NEWP Opens the door to machine language instructions but the programmer always has to open that door knowingly, right?
Hans
ESPOL was an acronym for Executive Systems Problem Oriented Language. As
I understand it, NEWP is not officially an acronym and doesn't stand for anything. The bit about washroom privileges was an in-plant joke that
got spread around. The other story about the origin of NEWP as a name
was that whenever someone would ask John McClintock (the chief
developer) whether the new compiler was ready to use yet, he'd reply "Newp."
1. The Mark II.1 SYMBOL/MCP (ca. 1972) was 25,376 lines. The MCP 12.0 SYMBOL/MCP (ca. 2008) was 1,282,948 lines.
2. To the best of my knowledge, there has never been any hard-coded
assembly language in the B6500 and later MCPs.
So SAFE in NEWP identifies parts of code that are in assembly language?
In C the term usually indicates improper use of pointer variables. Thiat language is very generous in offering options with unexpected side effects when using pointers.
NEWP Opens the door to machine language instructions but the programmer always has to open that door knowingly, right?
Hans
If I recall correctly, there was some work we had to do to allow a source file to exceed a million lines.
On Sunday, October 21, 2018 at 11:42:17 AM UTC-7, Paul Kimpel wrote:
ESPOL was an acronym for Executive Systems Problem Oriented Language.
<snip>
My recollection is that the P in ESPOL is for "Program" rather than "Problem."
<snip>
On Sunday, October 21, 2018 at 12:15:30 AM UTC-7, Hans Vlems wrote:code, but you could change your source code to coax the compiler into generating the machine code you wanted.
So SAFE in NEWP identifies parts of code that are in assembly language?
In C the term usually indicates improper use of pointer variables. Thiat language is very generous in offering options with unexpected side effects when using pointers.
NEWP Opens the door to machine language instructions but the programmer always has to open that door knowingly, right?
Hans
Unsafe constructs were provisions that allowed one to do things that system software needed, such as pausing other processors, altering a stack, etc. These were accomplished using language constructs rather than machine operators.
The old Programmer's Workbench editor allowed one to put the cursor on a source code line and use the "]" command to view the generated machine code. I used to do that fairly often when I was optimizing code. It didn't let you change the generated
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 231:32:43 |
Calls: | 6,624 |
Files: | 12,171 |
Messages: | 5,319,429 |