with such solution we will obtain bullshit.

This is the way squeak removed etoy: full of terrible case statements.

In vw you have bindings that are resolved when used but this is just one part of the story.

when you have a document and multiple outputer you should start to see how you can structure them
in a way that your model is independant from the outputers.

Alex will feel the pain if one day he has to port GraphEt to VW and for some strange reason
they want to use another frameworks than artefact or one of the used packages do not work in VW.

Good luck.

Now we can continue not to trust in modularity but we should not come back and cry when it will hurts
because it will hurt.

Stef

2014-06-27 8:38 GMT-03:00 Alexandre Bergel <alexandre.bergel@me.com>:

But this solve only partially the problem. How do you reference a class then?

I cannot write Smalltalk at: #myclass all the time

Another solution would be to put the code that does the exporting in a different package, but this is quite some work.

Have you explored instructing the compiler to accept unloaded class names and then associate those names with a block which load the package?

Hernán
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev