Sujet : Re: question about linker
De : david.brown (at) *nospam* hesbynett.no (David Brown)
Groupes : comp.lang.cDate : 11. Dec 2024, 21:36:48
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vjct50$1n22j$2@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
User-Agent : Mozilla Thunderbird
On 11/12/2024 17:51, Janis Papanagnou wrote:
On 11.12.2024 17:47, David Brown wrote:
On 11/12/2024 17:30, Janis Papanagnou wrote:
On 11.12.2024 09:43, Ike Naar wrote:
On 2024-12-09, Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:
An unambiguous grammar is something quite essential; how would you
parse code if it were ambiguous?
>
Here's an ambiguity in the C grammar:
>
[...]
>
The following selection-statement is grammatically ambiguous:
>
if (E1) if (E2) S1 else S2
>
Yes, the dangling else is a common ambiguity in many programming
languages.
>
That's why I prefer languages with syntaxes like in Algol 68 or
Eiffel (for example).
>
It is easy to avoid in a C-like language - simply require braces on "if"
statements, or at the very least, require them when there is an "else"
clause.
Yes, sure. But, I can't help, it smells like a workaround.
If C had that requirement, it would not be a workaround - it would be a fixed part of the grammar. The current definition of C, with optional braces and an extra "semantics" clause seems more like a workaround to me.
Most C coding standards and style guides make that requirement
- not because the C compiler sees it as ambiguous, but because humans
often do. (Or they misinterpret it.)
Yes, true. (We had that in our standards, too.)
Janis
question about linker
Re: question about linker