NXWriteTypes() of 'char *'

Article View: comp.sys.next.programmer

Article #1951

Back to comp.sys.next.programmer Previous Next

#1951

From: Chris Jackson IME
Date: Wed, 23 Dec 1992 13:19

15 lines
1061 bytes

My experience seems to suggest that using NXWriteTypes() to archive a 'char *'
only works if the 'char *' is not NULL.  If it *is* NULL, then a memory
violation results in 'strlen()' in NeXT code when the object concerned is read
from the archive.

Can anyone out there confirm that this is the case and whether or not it is the
expected behaviour ?  If it is the expected behaviour, I presume I have to
explicitly code around it ?  Next question - is there a recommended way of
doing
so ?

Thanks, in anticipation,

Chris.

Technical Details

Message-ID: <1992Dec23.131946.14537@rdg.dec.com>

Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!decwrl!deccrl!news.crl.dec.com!rdg.dec.com!uproar.enet.dec.com!jacksonc

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!decwrl!deccrl!news.crl.dec.com!rdg.dec.com!uproar.enet.dec.com!jacksonc
From: jacksonc@uproar.enet.dec.com (Chris Jackson @ IME)
Newsgroups: comp.sys.next.programmer
Subject: NXWriteTypes() of 'char *'
Keywords: NXWriteTypes
Message-ID: <1992Dec23.131946.14537@rdg.dec.com>
Date: 23 Dec 92 13:19:46 GMT
Sender: news@rdg.dec.com (Mr News)
Reply-To: jacksonc@uproar.enet.dec.com (Chris Jackson @ IME)
Organization: Digital Equipment Service Industries Solutions Company Ltd
Lines: 15