Message-ID: <3B950814.142AC1E5@attglobal.net>
Date: Tue, 04 Sep 2001 09:57:56 -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> <GJ4sCq.2rs@world.std.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 32.101.177.24
X-Trace: 4 Sep 2001 16:54:52 GMT, 32.101.177.24
Organization: Global Network Services - Remote Access Mail & News Services
Lines: 39
X-Complaints-To: abuse@prserv.net
Path: news.duke.edu!newsgate.duke.edu!news-hog.berkeley.edu!ucberkeley!news.maxwell.syr.edu!cpk-news-hub1.bbnplanet.com!washdc3-snh1.gtei.net!news.gtei.net!newsfeed.us.prserv.net!prserv.net!news3.prserv.net!32.101.177.24
Xref: news.duke.edu rec.arts.int-fiction:92119



Sean T Barrett wrote:
> >
> They don't work correctly with modules, I think. You might check
> deja^H^H^H^H groups.google.com for others...
>
> SeanB

Love that Google archive.  Searching it came up with a post of mine from
nine months ago, with the very same issue (I'd forgotten that the LAST
time I pulled this project out of mothballs, I had the same Infix problem.)

No answers then, either, but I was reminded of another peculiarity in
this problem, in that if I use one of the name properties to refer to an
object, instead of its source code name, Infix doesn't crash.  A Zorkian example:

Object Cellar "Cellar"
	with 	name "cellar" "basement",
	description "You are in a dark and damp cellar with a narrow passageway
				leading north, and a crawlway to the south. A trapdoor is
				visible in the ceiling. On the west is the bottom of a steep
				 metal ramp which is unclimbable.",
			u_to	trapdoor,
			s_to	East_Chasm,
			n_to	Troll_Room,
			w_to	"The steep metal ramp is unclimbable.";


Inputting ;x cellar causes the interpreter to crash.  ;x basement on the
other hand gets the proper output, no crash.

It's got to be something I've done in my code (I've tried reinstalling
infix.h in case it had been corrupted somehow) but I've got a feeling
I'm going to have to figure out the inner workings of infix (argh) and
start setting some breakpoints to find out just where things are getting
snarked up.

Chip
