Re: [Groff] Re: getopt() as gtroff macro ?

[Werner LEMBERG]

> > Would the .getopt request not need to also include the arguments
> > of the invoking macro?  Thus, this example would become:
> >
> >   .de foo
> >   .  getopt "foox" "ac:" "--all --check=" \\$@
> >   .  ...
> >   ..
> 
> Perhaps not, now that I've thought about it some more.  May I plead
> lack of alertness, due to insomnia and getting up too early? ;-)
> 
> Clearly, since we are considering implementing .getopt as a built-in
> request, rather than as a macro, it would be able to implicitly access
> the arguments of its containing macro, in much the same way as .shift
> must.  Of course, implementing it this way implies that it may only
> be used within the scope of a macro, but then, why would anyone want
> to use it anywhere else?

Actually, it could be optional.  Normally, you won't use it, but there
may be situations where you have to modify the arguments before
passing it to .getopt.


    Werner