Newsgroups: rec.arts.int-fiction
Path: nntp.gmd.de!news.rwth-aachen.de!news.rhrz.uni-bonn.de!news.uni-stuttgart.de!uni-regensburg.de!uni-erlangen.de!news.th-darmstadt.de!odb!mainz.rhein-main.de!pegasus.PFM-Mainz.de!blackbush.xlink.net!howland.reston.ans.net!newsfeed.internetmci.com!vixen.cso.uiuc.edu!usenet.ucs.indiana.edu!news.cs.indiana.edu!shulick@guava.ucs.indiana.edu
From: "Sam Hulick" <shulick@guava.ucs.indiana.edu>
Subject: Inform: Why the limitations?
Message-ID: <199512090606.BAA13729@guava.ucs.indiana.edu>
Organization: Vallen Software
Date: Sat, 9 Dec 1995 01:06:48 -0500 (EST)
Lines: 24


Unix Inform 5.5 (v1502/a)
1:#########################################################
line 31: Error: All 48 attributes already declared

.... and...

Unix Inform 5.5 (v1502/a)
1:#########################################################
line 43: Error: All 62 properties already declared

Why?  Why can't we bump these up with something like $MAX_ATTR or
$MAX_PROP on the command line?  Why this limitation?  Realistically,
there AREN'T a lot of attributes/properties you can alias, because they
are almost all already aliased, or unusable on rooms or items.  For
example, if I wanted to make an Attribute "small" to set on objects,
abou the only thing I could alias it off of is the 'visited' attrib.  If
it's this limited, why restrict to only 48 attributes and 62 properties?

-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Sam Hulick          % "The saddest words of tongue or pen are these:
% shulick@indiana.edu %  `It might've been.'"  --Anon.
% http://129.79.1.4/~shulick
