Re: wolf 3d-- BUG!

[Rubywand <rubywand@swbell.net>]

Nathan Mates writes ...
> 
> In article <34EF1811.84544F16@swbell.net>,
> Rubywand  <rubywand@swbell.net> wrote:
> ....
> 
> >     The OS was there first. However weird and quirky, its rules are the
> >ones programmers must play by-- either that, or supply a 'rule change'
> >with the program.
> 
>    Come on, you're reaching for more and more irrational explanations
> to try and justify your position. OS Bugs are *not* the responsibility
> of the app to clean up after;

     In so far as the supposed bug in the standard, widely installed OS
leads to a game bombing, the game programmers _must_ "clean up after"
the bug. If they do not, their game will BOMB. This is not a complex
concept.

     If the programmers release the game to the public, players will be
chapped when they encounter the _game_ BUG. Reviewers will print
reviews saying things like: "It's a nice game; too bad it's got a BUG
which  B O M B S  your system".


> the problem lies in the OS and should
> be fixed in there.
>

     Feel free. Meanwhile, Wolf-3D should be fixed so that it does not
crash when running under the standard OS. Many other GS games do not
crash; Wolf-3D should not crash, either.


> ....
> 
>    Your system of apps doing things based on the OS version is
> fundamentally stupid and will lead to much more problems. Fix bugs
> where the object code ended up, NOT wherever you feel like it.
>

     If programmers insist upon using calls like SetTSPtr, then they had
darn sure better pay attention to OS quirks.

     To quote another csa2 member's tagline:
     
>>

What are the facts? Again and again and again-- what are the _facts_?
Shun wishful thinking, avoid opinion, care not what the neighbors
think-- what are the facts, and to how many decimal places? -R.A.
Heinlein

<<

     Wolf-3D crashes. That is a fact. The game has a BUG, Sir, a big fat
BUG!


Rubywand