Re: question about linker

Bart <bc@freeuk.com> writes:
[...]

This is a discussion of language design. Not one person trying to
understand how some feature works. I could learn how X works, but that
won't help a million others with the same issue.

That's great, if there are a million other users who are confused
about the same things you claim to be confused about, and if you're
actually trying to help them.

Except for a couple of things.

I don't believe there are "a million other users" who are confused
about, to use a recent example, C's rules about whether a "}" needs
to be followed by a semicolon.  I've seen code with extraneous
semicolons at file scope, and I mostly blame gcc's lax default
behavior for that.  But I've never heard anyone other than you
complain about C's rules being intolerably inconsistent.

And even if those users exist, I don't see you making any effort
to help them, for example by explaining how C actually works.
(Though you do manage to provoke some of us into doing that for you.)

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */