Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!rutgers!bellcore!tness7!killer!dcs!wnp
From: wnp@dcs.UUCP (Wolf N. Paul)
Newsgroups: comp.unix.microport
Subject: Re: running "pcomm" on Sys V/AT
Keywords: de'reffing NULL pointers again
Message-ID: <207@dcs.UUCP>
Date: 19 Sep 88 12:06:05 GMT
References: <633@wa3wbu.UUCP> <424@l5comp.UUCP> <635@wa3wbu.UUCP>
Reply-To: wnp@dcs.UUCP (Wolf N. Paul)
Organization: DCS, Dallas, Texas
Lines: 23

In article <635@wa3wbu.UUCP> john@wa3wbu.UUCP (John Gayman) writes:
 >In article <424@l5comp.UUCP>, scotty@l5comp.UUCP (Scott Turner) writes:
 >> Deep in the heart of ports.c of pcomm you will find a if statement that
 >> checks *str != NULL || str != NULL. This needs to be reversed so that it
 >
 >       There is a file called port.c but not ports.c. And I searched
 >through all the occurances of "str" and there is no line like you
 >mention above. Can you clarify where it is located ? Thanks !

The line actually reads:

	if (*lock_path != NULL || lock_path != NULL) {

Scott thus used "str" as a generic name for a string, similar to the
way names are used in the "SYNOPSIS" portion of a typical UNIX manual
page. When the manual page says that "fopen()" is called as,
"fopen(file-name, type)", that doesn't mean that you always have to call
the first argument "file-name" and the second one "type".

Be a bit creative in interpreting USENET postings :-) ...
-- 
Wolf N. Paul * 3387 Sam Rayburn Run * Carrollton TX 75007 * (214) 306-9101
UUCP:     killer!dcs!wnp                 ESL: 62832882
DOMAIN:   dcs!wnp@killer.dallas.tx.us    TLX: 910-380-0585 EES PLANO UD