Commit 0b558962 by Alan Modra Committed by Alan Modra

* README.Portability: Fix typos.

From-SVN: r55164
parent 9a81c5b7
2002-07-02 Alan Modra <amodra@bigpond.net.au>
* README.Portability: Fix typos.
2002-07-01 Hans-Peter Nilsson <hp@axis.com> 2002-07-01 Hans-Peter Nilsson <hp@axis.com>
PR target/7177 PR target/7177
......
...@@ -123,8 +123,8 @@ int myfunc PARAMS ((double, int *)); ...@@ -123,8 +123,8 @@ int myfunc PARAMS ((double, int *));
int int
myfunc (var1, var2) myfunc (var1, var2)
double var1; double var1;
int *var2; int *var2;
{ {
... ...
} }
...@@ -132,7 +132,7 @@ myfunc (var1, var2) ...@@ -132,7 +132,7 @@ myfunc (var1, var2)
This implies that if the function takes no arguments, it should be This implies that if the function takes no arguments, it should be
declared and defined as follows: declared and defined as follows:
int myfunc PARAMS ((void)) int myfunc PARAMS ((void));
int int
myfunc () myfunc ()
...@@ -300,8 +300,8 @@ long and int are not the same size. ...@@ -300,8 +300,8 @@ long and int are not the same size.
Second, if you write a function definition with no return type at Second, if you write a function definition with no return type at
all: all:
operate(a, b) operate (a, b)
int a, b; int a, b;
{ {
... ...
} }
...@@ -314,8 +314,8 @@ Implicit function declarations always have return type int. So if you ...@@ -314,8 +314,8 @@ Implicit function declarations always have return type int. So if you
correct the above definition to correct the above definition to
void void
operate(a, b) operate (a, b)
int a, b; int a, b;
... ...
but operate() is called above its definition, you will get an error but operate() is called above its definition, you will get an error
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment