Newsgroups: rec.arts.int-fiction
Path: news.duke.edu!newsgate.duke.edu!nntp-out.monmouth.com!newspeer.monmouth.com!nntp.abs.net!uunet!dca.uu.net!ash.uu.net!world!buzzard
From: buzzard@world.std.com (Sean T Barrett)
Subject: Re: Inform objects help please!
Message-ID: <GLuMy4.LJr@world.std.com>
Date: Sat, 27 Oct 2001 05:22:52 GMT
References: <B7FCF8EC.1B5B%shanedoak@ripcurl.com.au> <9r6k090mgg@drn.newsguy.com> <GLs5qL.57F@world.std.com> <9ra4be$pg2$1@news.panix.com>
Organization: The World Public Access UNIX, Brookline, MA
Lines: 22
Xref: news.duke.edu rec.arts.int-fiction:93986

Andrew Plotkin  <erkyrath@eblong.com> wrote:
>Does this hypothesis include trying the transparent-noncontainer
>solution, to see if it's what you want?

I hypothetically had thought I had hypothetically tried
making a transparent non-container and it still printed
its children, but I could hypothetically have been totally
confused and tested it wrong and ended up with an unnecessary
hack.

>"I have observed no bugs" is, um, not a very comforting statement.
>Have you gone through the library source searching for "concealed", to
>analyze how each piece of "concealed" code interacts with your use of
>that attribute?

No, and I certainly would before suggesting it as a patch to
the library in general.

But it's all irrelevant, I think, if the transparent non-container
works as desired.

SeanB
