Newsgroups: rec.arts.int-fiction
Path: news.duke.edu!newsgate.duke.edu!nntp-out.monmouth.com!newspeer.monmouth.com!news.tele.dk!62.112.0.25!newsfeed.online.be!zur.uu.net!ash.uu.net!world!buzzard
From: buzzard@world.std.com (Sean T Barrett)
Subject: Re: [Inform Question] Test for identical objects
Message-ID: <GF9yzC.Bwz@world.std.com>
Date: Thu, 21 Jun 2001 10:11:35 GMT
References: <9gqvp7$8kb$1@diana.bcn.ttd.net> <3b310b6b$0$1926$b45e6eb0@senator-bedfellow.mit.edu> <GF93Cy.60F@world.std.com> <3b312ca2$0$1919$b45e6eb0@senator-bedfellow.mit.edu>
Organization: The World Public Access UNIX, Brookline, MA
Lines: 19
Xref: news.duke.edu rec.arts.int-fiction:88985

Jake Wildstrom <wild_dj@mit.edu> wrote:
>Sean T Barrett <buzzard@world.std.com> wrote:
>>If it doesn't *always* work, I wouldn't bother. And, unfortunately,
>>making it *always* work is a huge endeavor.
>
>Well, there is a simple one that would always work, but it's kind of slowish:
>
>Turn objectloop(x in y)... into objectloop(x) if(x in y)...

Ok, good point, heh. Inform has an advantage in this case
over most languages and iteration situations.

But *technically* it doesn't satisfy my demands for a robust
iterator, because the handling of newly-created objects is
inconsistent (if an object is created during the objectloop,
it *might* get tested by the objectloop or it might not, if
I'm imagining how dynamic object creation works correctly).

SeanB
