Re: do { quit; } else { }

On 09/04/2025 12:11, Michael S wrote:

On Wed, 9 Apr 2025 11:42:36 +0200
David Brown <david.brown@hesbynett.no> wrote:
 

>
This applies to all languages.  For example, in Python you do not
have separate "interface" and "implementation" files - everything is
in one ".py" file.  If I have a Python module that says "import
my_py_lib", how does Python know where to find "my_py_lib.py" ?  How
does it know which copy of "my_py_lib.py" to use from the dozen that
I have on my computer? The answer is it uses some default rules for
the language, some default rules for the implementation, some
configuration settings, some flags, some run-time information
(equivalent to compile-time information in compiled languages).  The
exact details are different, but the principle is the same for C and
for any other language that can handle more than one file.
>

 It is not quite the same for all languages. The degree in which it is
standardizes vs left to implementation differs. In some languages it is
fully standardized.
I think, in case of Ada it was standardized in APSE. But then, real
world mostly accepted a language part of Ada standard and mostly
ignored APSE part.
 

As I said, details vary, and some languages may specify more details than others.  There are also differences in the relationship between a "module" of some sort that a unit might refer to, and the file or files that comprise that module.  But the principle is that when one unit refers to another, the tools will have some way of figuring out which unit you are referring to, distinguishing it from other units or files on the same host system even if the filenames are the same.  C does not differ in principle here from other languages.  Bart seems to think C is somehow especially bad or complicated - he is wrong in that.