diff options
author | Neil Booth <neilb@earthling.net> | 2000-07-16 13:35:23 +0000 |
---|---|---|
committer | Neil Booth <neil@gcc.gnu.org> | 2000-07-16 13:35:23 +0000 |
commit | f67798e710a953e91994ad1ff9bb3f458dfbef6c (patch) | |
tree | b0c9d9345b06aeca451f4412634176000d523856 /gcc/README.Portability | |
parent | bf4467813b6b51c4eabaf8b4865c1e4ac09b0ad9 (diff) | |
download | gcc-f67798e710a953e91994ad1ff9bb3f458dfbef6c.tar.gz |
cpplex.c: Update comments.
* cpplex.c: Update comments.
* README.Portability: Small update.
From-SVN: r35058
Diffstat (limited to 'gcc/README.Portability')
-rw-r--r-- | gcc/README.Portability | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/gcc/README.Portability b/gcc/README.Portability index 43efc39f3c3..d69c3869b3f 100644 --- a/gcc/README.Portability +++ b/gcc/README.Portability @@ -46,6 +46,10 @@ should be written free ((PTR) h->value.expansion); +Further, an initial investigation indicates that pointers to functions +returning void are okay. Thus the example given by "Calling functions +through pointers to functions" below appears not to cause a problem. + String literals --------------- @@ -87,7 +91,7 @@ needs to be coded in some other way. signed keyword -------------- -The signed keyword did not exist in K+R compilers, it was introduced +The signed keyword did not exist in K+R compilers; it was introduced in ISO C89, so you cannot use it. In both K+R and standard C, unqualified char and bitfields may be signed or unsigned. There is no way to portably declare signed chars or signed bitfields. |