Thanks Damian,
That's actually where I started from as well! Except file names after
the ".so" can have spaces in them on some platforms, and I don't believe
there is a requirement to escape them, so something like this would be
valid:
.SO /my/source/file with spaces in the name.c
So the idea of putting the range specifier at the front gets around that.
Also easy enough to be compatible with the older AT&T syntax (no space
after the ".so[S-E]").
I'll keep polishing it and using it in anger to make sure it does what
is needed. I think the need for multiple ranges is a nice-to-have but not a
necessity as it can be synthesized with multiple .so calls: your example
would be:
.SO /my/source/file 2-11
.SO /my/source/file 40-50
.SO /my/source/file ...
With my alternative syntax:
.SO[2-11] /my/source/file
.SO[40-50] /my/source/file
.SO[...] /my/source/file
Cheers,
Neil
On Wed, 19 Feb 2025 at 22:35, Damian McGuckin <dami...@esi.com.au> wrote:
> On Wed, 19 Feb 2025, Neil Johnson wrote:
>
> > .so[2-11] /my/source/file.c
>
> A long time ago, I did something like
>
> .SO /my/source/file 2-11,40-50,...
>
> and some variations which had a label to delimit sections.
>
> Eventually, the reason for that disappeared and the sode for my special
> soelim got lost during an upgrade.
>
> Thanks - Damian
>
