> Yes. In the request index there are names and page numbers,
> e.g. `pnr ... 168' If one is looking for a function but
> does not know the request's name, it takes a long time to find what
> one wants. Try this, no, try that, no, try this, yeah.
>
> However, if there was some text b
Yes. In the request index there are names and page numbers, e.g.
`pnr ... 168'
If one is looking for a function but does not know the request's
name, it takes a long time to find what one wants.
Try this, no, try that, no, try this, yeah.
However, if there was some text between r
> Just out of interest. As someone who hates typing a lot and loves
> silly 2 character names, I would write a Perl script to list and
> sort number registers in source files. Is there a utility that does
> that regarding groff and other compiled companions? Perhaps done
> using the source just
Werner thank you,
Just out of interest. As someone who hates typing a lot and loves
silly 2 character names,
I would write a Perl script to list and sort number registers in
source files.
Is there a utility that does that regarding groff and other compiled
companions?
Perhaps done using th
> Groff is a programming language, sort of. I wonder whether already
> exist a scope-separating mechanism for number registers,
No.
> just I do not know about it, or is there such a thing in the
> pipeline in the future?
Yes.
> If you mistype the name of a macro, it won't get executed, and in
>
Happy New Year Folks,
Programming languages are keen on formal mechanisms to make the scope
of variables clear.
If you write a subroutine in Fortran, everything is local, if you want
global reach, you need to work on common.
In Perl, everything is common, if you want local, you have to work o
