Gale Paeper wrote:
The prose describing the semantics is pretty dense already; just imagine what it would be like if there wasn't any convenient handles to associate the semantic prose to the syntax.
I don't want to go into this too deeply, because it might get rather ugly. If they really cared about a readable language, there are dozens of ways to do so, without affecting the BNF syntax.
So, I'll forbid this wrong form again. Now GPC will allow 1., 2., 1. and 2. in one source file, 3. and a "GPC specific form" (which may also be PXSC compatible) without any explicit export part.
Although I think it would be a major headache to implement, I'll note that for full compliance you can't restrict the number of program-components in a source file nor require any ordering other than the parial ordering of the define-before-use 6.2.2.9 requirement. (I'm just noting the requirement and not suggesting that GPC must fully implement the requirement.)
Where does the standard say anything about source files?
Frank