🚀 go-pugleaf

In article <6243@uceng.UC.EDU> dsims@uceng.UC.EDU (david l sims) writes:

>error messages. One particularly annoying message says at the end
>of the program, "null pointer assignment." I have no idea where
>I assigned some value to a null pointer, and even if I did, it doesn't
>seem to effect my programs. I don't like this statement coming up
>at the end of my program. Is there any way to turn run time error
>messages off? 

OUCH!! This one's gonna' bite you in the arse eventually. You're program is
doing a wild write into memory. Change the environment and you could see some
nasty *a*ffects.

> Does TC give any assistance in tracking down this error.

Well, do you have the debugger? I had this problem... once :^) and when I ran
the debugger the environment was changed enough that the affect of this "null
pointer" was quite obvious.

Don't let this ride. It is something that you need to find!

-- 
  **********************************************************************
     Chuck Anderson                    uucp     : uunet!isis!nyx!cla
     Boulder, Co. (303) 494-6278       internet : cla@nyx.cs.du.edu
  **********************************************************************