Message-ID: <3CB64B57.D98AB07A@attNOSPAMglobal.net>
Date: Thu, 11 Apr 2002 19:49:58 -0700
From: Chip Hayes <chiphayes@attNOSPAMglobal.net>
X-Mailer: Mozilla 4.72 (Macintosh; U; PPC)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: rec.arts.int-fiction
Subject: Re: Puzzling Nitfol error
References: <3cb4f7e9_3@news3.prserv.net> <8df06e254b.kevin@bracey-griffith.freeserve.co.uk> <3CB5A7B4.382412BC@attNOSPAMglobal.net> <c85491254b.kbracey@kbracey.cam.pace.co.uk> <3CB64740.A63E6206@attNOSPAMglobal.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 32.100.7.155
X-Trace: 12 Apr 2002 02:47:37 GMT, 32.100.7.155
Organization: Global Network Services - Remote Access Mail & News Services
Lines: 22
X-Complaints-To: abuse@prserv.net
Path: news.duke.edu!newsgate.duke.edu!nntp-out.monmouth.com!newspeer.monmouth.com!priapus.visi.com!news-out.visi.com!hermes.visi.com!uunet!ash.uu.net!newsfeed2.us.prserv.net!prserv.net!news3.prserv.net!32.100.7.155
Xref: news.duke.edu rec.arts.int-fiction:102951



>
> Okay, I've tried using the small sample program included in NPC_Engine
> and it does NOT give the same error. Something in his Deadline port and
> in my code must be doing it... back to sleuthing some more.
>

The reason that the demo program doesn't throw an error: none of the
NPC's have a describe property.

But giving one of them a describe -- even a routine as simple as a
single print statement -- results in the error. So something in the
NPC_Engine must be doing it (unless it's some obsure oddity in the
library's handling of describe).

If you're up for it, download NPC_Engine, add a describe prop to one of
the demo program's NPCs, then run it Nitfol and you'll see what I mean.

Just wish I knew why...

Chip
