Re: wolf 3d-- bug? -- the culprit?

[Rubywand <rubywand@swbell.net>]

Nathan Mates writes ...
> 
> In article <34EF0D51.80A1837F@swbell.net>,
> Rubywand  <rubywand@swbell.net> wrote:
> > One suspects that Hierarchic messes with a toolset pointer and that
> > Wolf-3D diddles the same toolset's pointer.
> 
>    As I've said many times, this problem is exposed by apps doing some
> things. Hierarchic is *not* an app. Thus, this bug cannot apply to
> it.

     Hierarchic does not have to be an application (no one said it is)
in order to modify a toolset pointer. My idea is that, once anything
modifies a toolset pointer, any later attempt to modify that toolset's
pointer could produce problems if the later mod assumes that the
toolset's pointer has not been modified.

     Hierarchic may be perfectly blameless. That removing Hierarchic
from SYSTEM/System.Setup does appear to eliminate Wolf-3D exit crashes
is nice for users to know and, for Wolf-3D programmers, it may be useful
information.

> What part of that progression do you not understand? You seem to
> have become irrationally attached to hierarchic being at fault, and
> refuse to listen to facts about a bug that directly contradict your
> thinking.
>

     So far, there have been no facts, just claims. Earlier you said
that you could prove, with code, that a bug exists in the OS which
explains the Wolf-3D crashes. Okay; list the code and explain the bug.


Rubywand