Newsgroups: rec.arts.int-fiction
Path: nntp.gmd.de!news.ruhr-uni-bochum.de!news.rhrz.uni-bonn.de!RRZ.Uni-Koeln.DE!news.gtn.com!news.frankfurt.ecrc.net!news.ecrc.de!newsfeed.sunet.se!news00.sunet.se!sunic!mn6.swip.net!solace!eru.mt.luth.se!news.algonet.se!eua.ericsson.se!cnn.exu.ericsson.se!newshost.convex.com!bcm.tmc.edu!pendragon!ames!enews.sgi.com!news.sgi.com!nntp-hub2.barrnet.net!cpk-news-feed2.bbnplanet.com!cam-news-hub1.bbnplanet.com!howland.erols.net!tank.news.pipex.net!pipex!dish.news.pipex.net!pipex!canon.co.uk!neilb
From: neilb@canon.co.uk (Neil Bowers)
Subject: [Inform] implicit vs explicit short_name?
X-Nntp-Posting-Host: tardis
Message-ID: <Dy8DIp.2qq@canon.co.uk>
Sender: news@canon.co.uk (USENET News)
Organization: Canon Research Centre Europe, Ltd.
X-Newsreader: TIN [version 1.2 PL2]
Date: Tue, 24 Sep 1996 09:40:00 GMT
Lines: 25

Hi,

If you have an object declared thusly:

	Object foo "foo bar";

then an attempt to set foo.short_name will cause a run-time error,
because short_name has not been explicitly declared. So the object
should be declared:

	Object foo
	    with
		short_name "foobar";

Is there any overhead to declaring an object this way, if you're not
going to mess with foo.short_name?

If there is no overhead, then maybe an idea for a future Inform feature
would be to automatically declare short_name if you use the first style
of object declaration?

neilb
--
When someone tells you something defies description, you can be pretty sure
he's going to have a go at it anyway.                   -- Clyde B. Aster
