scc

commit 80786a2342984eefadc4b2b1c6402dacbb57bfa8
parent c3a50031fc81663f985a3abfc0efa2c0ea3ee5eb
Author: Roberto E. Vargas Caballero <k0ga@shike2.com>
Date:   Mon, 20 Mar 2017 16:21:09 +0100

Add more comments in README

Some ppl believed that I was wrong about my comments, but this too small
examples will help them to see what are the points.

Diffstat:
M
README
 | 
16
++++++++++++++++

1 file changed, 16 insertions(+), 0 deletions(-)
diff --git a/README b/README
@@ -53,6 +53,14 @@ grammar ambiguous because it is impossible to differentiate between:
         (int (f))  -> function returning int with one parameter of type f
         (int (f))  -> integer variable f
 
+If you don't believe me try this code:
+
+int
+f(int g())
+{
+	return g();
+}
+
 Function type names are stupid, because they are used as an alias
 of the function pointer types, but it is stupid that something
 like sizeof(int (int)) is not allowed (because here it should be
@@ -71,3 +79,11 @@ have external linkage and file scope. The type of the variable
 is the composition of all the definitions find in the file. The exact
 rules are a bit complex (3.7.2), and SCC ignores  them at this moment
 and it does not allow any definition of variables with incomplete type.
+
+If you don't believe me try this code:
+
+struct foo x;
+
+struct foo {
+	int i;
+};