aboutsummaryrefslogtreecommitdiff
path: root/gcc/README.Portability
diff options
context:
space:
mode:
authorAlan Modra <amodra@bigpond.net.au>2002-07-02 00:15:42 +0000
committerAlan Modra <amodra@gcc.gnu.org>2002-07-02 09:45:42 +0930
commit0b558962c137955bccb445d01c61c8d370212526 (patch)
tree9877ea1c16d720ab5185440fa2e2220984e0573e /gcc/README.Portability
parent9a81c5b7118435fb50a40f464946e960e01d7777 (diff)
downloadgcc-0b558962c137955bccb445d01c61c8d370212526.zip
gcc-0b558962c137955bccb445d01c61c8d370212526.tar.gz
gcc-0b558962c137955bccb445d01c61c8d370212526.tar.bz2
* README.Portability: Fix typos.
From-SVN: r55164
Diffstat (limited to 'gcc/README.Portability')
-rw-r--r--gcc/README.Portability14
1 files changed, 7 insertions, 7 deletions
diff --git a/gcc/README.Portability b/gcc/README.Portability
index dba1240..04638b2 100644
--- a/gcc/README.Portability
+++ b/gcc/README.Portability
@@ -123,8 +123,8 @@ int myfunc PARAMS ((double, int *));
int
myfunc (var1, var2)
- double var1;
- int *var2;
+ double var1;
+ int *var2;
{
...
}
@@ -132,7 +132,7 @@ myfunc (var1, var2)
This implies that if the function takes no arguments, it should be
declared and defined as follows:
-int myfunc PARAMS ((void))
+int myfunc PARAMS ((void));
int
myfunc ()
@@ -300,8 +300,8 @@ long and int are not the same size.
Second, if you write a function definition with no return type at
all:
- operate(a, b)
- int a, b;
+ operate (a, b)
+ int a, b;
{
...
}
@@ -314,8 +314,8 @@ Implicit function declarations always have return type int. So if you
correct the above definition to
void
- operate(a, b)
- int a, b;
+ operate (a, b)
+ int a, b;
...
but operate() is called above its definition, you will get an error