Re: question about linker

On 06/12/2024 19:41, Bart wrote:

On 06/12/2024 15:41, David Brown wrote:

On 05/12/2024 16:29, Bart wrote:

On 05/12/2024 14:00, David Brown wrote:

On 04/12/2024 22:31, Bart wrote:

>

And while you are at it, buy a better screen.  You were apparently unable to read the bit where I said that /saving typing/ is a pathetic excuse.

>
I can't type. It's not a bad excuse at all. I have also suffered from joint problems. (In the 1980s I was sometimes typing while wearing woolen gloves to lessen the impact. I haven't needed to now; maybe I've slowed down, but I do take more care.)

>
Being unable to type, on its own, is not a good excuse - it's an essential skill for productive programmers.

 

The goal of that last part is to reduce the number of characters you have to type, rather than the number of characters in the source code.

 My language:
    println =a,=b                  # 13 characters, 0 shifted
 

Since some of us live in a world with more than one person - indeed, more than one country - you might like to know that "=" is shifted on many keyboards.

(And that space is optional!)

The biggest irritation I have with your style, whether in your language or in C, is the lack of space.  It's a big key - it's easy to press. Good spacing habits (in the broadest sense) is the single biggest factor to readability of code, text, hand-writing, and pretty much anything else.
The language Forth is not known for being easy to read amongst non-experts, but one thing it gets right is insisting that there are spaces between tokens.

In C (assume the existence of stdio.h):
    printf("A=%lld B=%f\n",a,b);   # ~28 characters, 8 shifted
 Enough said.

I don't know what you are getting at, so I don't know if enough has been said or not.  If you are trying to suggest that the only thing you think is important about language syntax is how you print out two variables in as few keystrokes as possible, then I suppose you have succeeded in that goal, and can therefore rest your case.

 

  If I am writing module X and I want to use symbol "foo" from module Y, then I expect to say explicitly that I am using module Y (via an "import" or "include" statement), and I expect to say explicitly that I want "foo" from module Y (as "Y.foo", "Y::foo", "using Y", "using Y.foo", "from foo import Y", or whatever suits the language).
>
When I read a source file in any language, and I see the use of an identifier "foo", I want to know where that came from - I want to be able to find that out without doubt.  If it is written "Y.foo", then there is no doubt.  If I see "using Y.foo", there is no doubt - but I'd

 If you used my language, you can type Y.foo if you want. Nothing stops you doing that.
 

Look up - you might see the point flying overhead.

And if you were using it, I can make the ability to omit 'Y.' optional.
 However, you'd need to get used to a language and compiler that is 'whole-program', with a slightly different approach
 

You have snatched defeat from the jaws of victory in order to save a couple of lines at the start of each file - with the result that your language is only suitable for small single-developer programs.

 It is suitable for a vast number of programs. I'm sure it could be used for multi-developer projects too. After all, don't your projects also place all project-structure info into /one/ makefile? Which developer has editing rights on that file?

People who have something to contribute can change it.  Helpfully, files are found automatically by make, so changes are rarely needed.  (It makes perfect sense that all files in the source directories are part of the project - it does not make sense that all files in the directories are part of the namespace of all other files.)

 Who decides what the modules are going to be? If one developer decided they need a new module, what is the procedure to get that added to the makefile?
 

They put the file in the appropriate source directory (or add an appropriate source directory if needed).
(I started writing more, but I don't think it would be helpful to anyone.)