TIP: Click on subject to list as thread! ANSI
echo: c_echo
to: Jasen Betts
from: Robin Sheppard
date: 1999-01-20 21:54:04
subject: Null pointer assignment

RS>  JR> Null pointer assignment
 RS>
 RS>    should tell you where in your source code the error is,
 RS>    ie, what line number.

 JB> Often the compiler only checks *NULL on exiting, if at all.

   Yeah, someone else pointed that out, and both of you are right.  
   The compiler doesn't do any pointer checking, but if a runtime 
   error results from referencing a NULL pointer, that's when an error 
   message is displayed.  So, it's not as easy to track down as I 
   implied.  :/

... "He's dead, Jim."  "Ensign Dahmer, stop that!"
___ Blue Wave/DOS v2.30 [NR]

--- Maximus 2.01wb
* Origin: Basic'ly Computers: Mooo-ing Right Along. (1:153/9)
SEEN-BY: 396/1 632/0 371 633/260 262 267 270 371 634/397 635/506 728 639/252
SEEN-BY: 670/218
@PATH: 153/104 2 716 7715 140/1 396/1 633/260 635/506 728 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.