On Fri, Jul 10, 2009 at 6:59 PM, Igor Stasenko <siguctua at gmail.com> wrote:

> 2009/7/10 David Goehrig <dave at nexttolast.com>:
>
> I think its defined once in TPureBehavior , rest is inherired through
> traits.
> The problem that you can't see it, is browser, which shows trait
> method in class(es) which using them.
>

Hrmmm... that could be interesting to test... That of course begs the
question, if that behavior be vectored in TPureBehavior, and then apply
traits further throughout the remaining ones...

Being able to plug-in a custom parser/compiler to workspace would be useful.
> Because i have parser, which is a heavy refactoring of Squeak one, but
> it needs a bit more efforts to get a final shape.


 Thanks to the old hooks in ParagraphEditor, hooking up a custom parser /
compiler to a workspace doesn't require overwriting any existing class.  But
it isn't exactly straight forward. :)  And considering the parser get
repurposed for pretty printing and other tasks, it would be nice to be
certain the right parser is being used.

What I'd like to try is setting up multiple parser/compilers at a top
level, where some modules/packages compile against one Compiler, and
others compile against
others.



-- 
-=-=-=-=-=-=-=-=-=-=- http://blog.dloh.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20090710/0f06afe3/attachment.htm