Re: question about linker

Bart <bc@freeuk.com> wrote:

On 02/12/2024 21:06, David Brown wrote:

On 02/12/2024 19:27, Bart wrote:

On 02/12/2024 15:24, David Brown wrote:

On 02/12/2024 13:24, Bart wrote:

>

I would consider any kind of automatic import system to be a bad idea.

>
It's not automatic; you have to list the modules. If you don't want
data shared, then don't export it!
>

 
As I understood it, or perhaps failed to understand it (after all, it's
not as if there are published specifications, references,

 
https://github.com/sal55/langs/blob/master/Modules24.md
 
(A summary, mainly for my benefit, about a year old.)
 

tutorials or
examples for your language)

 
I gave an example in my post, of the lead module for my C compiler.
Older examples are in that link.
 
In all (counting the 'pcl' backend library) it comprises 36 source files
in two folders; plus about 40 C headers in two folders, which are
embedded into the executable.
 
This information is enough for the compiler, and nothing else, to locate
all the necessary files and to build an EXE file.

Your example does not show if you can have function with the same
name say 'fun1' in two different modules say 'A' and 'B'.  We
want use of 'fun1' in module 'C' to refer to 'fun1' in 'A' and
use of 'fun1' in module 'D to refer to 'fun1' in 'B'.  'A', 'B',
'C', 'D' and possibly other modules are supposed to be linked
together.

you would list your modules for a program
in one place, and then other modules in the program automatically import
them all.

 
The logic used in the name resolution pass of the compiler allows
visibiliy without needing full name-qualifying.

Most module system allows this, so really nothing new here.

I can rename any module, and I only need to change the one file. I can
move an exported function from one module to another, without making any
other changes (eg. change all xxx.F() to yyy.F()).

In one system that I use module names are independent of file names.
I can rename file contaning a module and this is change of single
line in a Makefile (could be 0 lines with more fancy Makefile, but
I want to have explit list of files).  When renaming a module, I
need to change all places that reference it.  For me it is not
a big deal, that normally is few minutes of work (in most cases
I could get away with simple mass search/replace which is single
longish command line in the shell, but I prefer to be careful
here) and is resonably infrequent.  Note that in my case module
names are part of "user interface", so I want to keep this
resonably stable to limit impact on the users.

--
                              Waldek Hebisch