Patch to make DefMod compile with SWILib

[Timothy Baldwin]

On Wednesday 25 July 2001 1:02 am, you wrote:
> On 24 Jul 2001, in message
> <E15P7mh-0005Hz-00 at bfg.reinhouse.freeserve.co.uk>,
>
> Timothy Baldwin <tim at reinhouse.freeserve.co.uk> wrote:
> > And make DefMod use the new oslib directory.
> >
> > Should be self explaintory.
>
> [snip]
>
> Well, thanks for your input, but as I've asked you before, will you please
> explain why you think this is necessary, and worthy of my spending time on
> checking it out, and implementing it.
>
> Defmod compiles quite happily in my environment; most users aren't
> interested in DefMod itself, but in its output. As far as I can see, it
> ain't broken; it don't need fixing.
>
> If you need to modify Defmod to run in your environment, then go ahead, but
> I can't see how this benefits anyone else.
>
> Do any other users/maintainers have different views?

The last paragraph of the "Implementation notes" section of 
!OSlib.Tools.DefMod reads:

> There is a small bootstrapping problem: DefMod is actually a client of
> OSLib. In order to build DefMod, there is therefore an implementation of
> the parts of OSLib that DefMod needs, as macros (using _swix()). This is
> called SWILib. In principal, these could now be replaced with the output of
> DefMod -l, but this would be to introduce a potentially lethal feedback
> loop.

If that is no longer intended behaviour, please amend to documentation.