godzil/ack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

m_a_i_n --> _m_a_i_n

Browse Source
This commit is contained in:
ceriel
1991-03-06 14:26:16 +00:00
parent 76d79cf17a
commit b893ec7013
38 changed files with 57 additions and 72 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/em/env.nr
View File

@@ -8,7 +8,7 @@ The remaining way to interact, interrupts, will be treated
together with traps in chapter 9.
.S2 "Program starting and stopping"
EM user programs start with a call to a procedure called
m_a_i_n.
_m_a_i_n.
The assembler and backends look for the definition of a procedure
with this name in their input.
The call passes three parameters to the procedure.
@@ -45,7 +45,7 @@ The
is terminated by a zero pointer.
.P
An EM user program stops if the program returns from the first
invocation of m_a_i_n.
invocation of _m_a_i_n.
The contents of the function return area are used to procure a
wordsized program return code.
EM programs also stop when traps and interrupts occur that are

2
doc/i80.doc
View File

@@ -545,7 +545,7 @@ stackpointer are set to 0x1000 and 0x8000 respectively.
.br
Other systems require other values.
.IP 2)
In 'head_em': before calling "_m_a_i_n", the environment
In 'head_em': before calling "__m_a_i_n", the environment
pointer, argument vector and argument count will have to be pushed
onto the stack.
Since this back-end is tested on a system without any knowledge

2
doc/z80.doc
View File

@@ -36,7 +36,7 @@ stackpointer are set to 0x1000 and 0x7ffe respectivally.
The latter because it could run on a 32K machine as well.
Other systems require other values.
.IP 2)
In \fIhead_em\fP: before calling "_m_a_i_n", the environment
In \fIhead_em\fP: before calling "__m_a_i_n", the environment
pointer, argument vector and argument count will have to be pushed
onto the stack.
Since this back-end is tested on a system without any knowledge