6 Oct
2007
6 Oct
'07
10:43 p.m.
i'm attempting to port magritte to GemStone, from what i understand main reason
MACondition class exist is so that block context can be serialized and stored.
Phillipe pointed out that GemStone support block directly. so in GemStone MACondition
would not be needed, i was going to remove MAConditons for the GemStone port, and
implement #asCondition on a Block to return self, so any code that used #asConditon would
still work Gemstone. is that okay.
From: renggli(a)iam.unibe.ch> Subject: Re: Magritte
MAConditionBuilder> Date: Sat, 6 Oct 2007 08:47:33 -0500> To:
smallwiki(a)iam.unibe.ch> > > hey guys in magritte MAConditionBuilder is a subclass
of > > protoObject not> > object. what is the reason for this.> > Check
out the references of MAConditionBuilder.> > The comment says:> >
BlockContext>>asCondition> "Convert the receiver to a condition, e.g. a
parse tree > representing the condition within the block. This is done by passing >
a proxy into the block and manually building a tree of conditions. > This doesn't
work for all code, but has the big advantage to make it > fully
serializeable."> > I rarely use this feature anymore. This is only useful if
you want > your conditions not to be block contexts (e.g. to serialize them).> >
I guess the whole condition code could be removed, unless somebody > opposes?> >
Lukas> > -- > Lukas Renggli> http://www.lukas-renggli.ch> > >
_______________________________________________> SmallWiki, Magritte, Pier and Related
Tools ...> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_________________________________________________________________
New music from the Rogue Traders - listen now!
http://ninemsn.com.au/share/redir/adTrack.asp?mode=click&clientID=832&a…