Message-ID: <3B957D56.3352903@attglobal.net>
Date: Tue, 04 Sep 2001 18:18:14 -0700
From: Chip Hayes <jwhayes@attglobal.net>
X-Mailer: Mozilla 4.72 (Macintosh; U; PPC)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: rec.arts.int-fiction
Subject: Re: [Inform] Infix problems...
References: <3B945A26.55BE7FBE@attglobal.net> <20010904160406.24764.00004869@mb-fm.aol.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 32.100.7.47
X-Trace: 5 Sep 2001 01:15:10 GMT, 32.100.7.47
Organization: Global Network Services - Remote Access Mail & News Services
Lines: 40
X-Complaints-To: abuse@prserv.net
Path: news.duke.edu!newsgate.duke.edu!solaris.cc.vt.edu!news.vt.edu!news.cc.ukans.edu!newsxfer.eecs.umich.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!jfk3-feed1.news.digex.net!intermedia!news.stealth.net!newsfeed.nyc.globix.net!uunet!ash.uu.net!newsfeed2.us.prserv.net!prserv.net!news3.prserv.net!32.100.7.47
Xref: news.duke.edu rec.arts.int-fiction:92164



OKB -- not okblacke wrote:
>
> Chip Hayes jwhayes@attglobal.net wrote:
> >Are there any known problems with the Infix suite?
>
>      There are a few that I know of.  The period and comma used for calling
> properties (as in "; obj.prop(foo,bar,baz)") don't work right, although I don't
> think this is a crash-inducing problem.
>
>       If it's actually crashing, one thing to watch out for is what you put in
> object properties.  I know that the "showobj" verb has this problem, and I
> wouldn't be surprised if Infix had a similar problem.  The problem occurs when
> you have property data which isn't what it appears to be.  For example, a raw
> number can be mistakenly interpreted as a dictionary word, and then when the
> library tries to "print (address)" it crashes because it's not really a
> dictionary word.
>

Yes, it's actually crashing.  Hard and ugly.  And none of your helpful
suggestions seem to apply to my code.

I suppose the first thing I should do is move it all over to my PC and
see if it's MAC specific.

If not, any suggestions on debugging interpreters?  I've heard Nitfol on
the PC has some debugging capability.  Or perhaps I really need to dive
into Infix, learn how it works, and try setting breakpoints to see where
it all goes south.

Could one bad object be affecting many others?  i.e. does Infix travel
down the object tree to reach a specific object... one bad branch and
the rest of the tree is screwed?  Or does it have a look-up table of
object numbers, then goes right to the object requested before printing
out its analysis?  And why would it crash on the object's source code
name, but give the proper output if you input one of the object's name'd
properties? <scratching head>

Chip
