Sujet : Re: Duplicate identifiers in a single namespace
De : blockedofcourse (at) *nospam* foo.invalid (Don Y)
Groupes : sci.electronics.designDate : 16. Oct 2024, 22:17:54
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vepai9$2dfrb$1@dont-email.me>
References : 1 2 3
User-Agent : Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2
On 10/16/2024 7:36 AM, Joe Gwinn wrote:
Pascal
If you declare multiple identifiers in the same namespace
you are hit on the head. You can have nested namespaces
and there is no conflict, the inner namespace counts.
Pascal is compiled in a single pass through the source code, so
everything must be defied before it is first used. Unlike C/C++,
which has a multipass compiler and linker. This was done because
Pascal was intended for teaching programming, and the load in the
university's computers was from compiling buggy student homework code
time and time again, while C was intended to replace assembly in the
Unix operating system.
I think you are misassigning effect to cause. Wirth was
obsessed (?) with simplicity. Even at the expense of
making things *harder* for the developer! (shortsighted,
IMHO).
Requiring the developer to declare his *future* intention
to reference an object *could* be seen as simplifying the
process -- at least from the compiler's point of view.
But, I've no fond memories of *any* language where I was
forced to do something that the compiler could very obviously
do; how is making MORE work for me going to make things better?
I share his belief that things should be "simpler instead of
more complex". But, that only applies to the decomposition
of a problem; the problem itself defines its complexity.