On 23. feb.. 2009, at 15.40, Rickard Öberg wrote: >>> >>> Changing these kinds of things at runtime is just bad practice and >>> will >>> lead to unreadable software, so we don't support this. >> >> That's understandable, but you know how I really like to push things >> beyond the limit to prove a point ;-) > > And the point is...? All I can see so far is that you want something > that can do what you say. But not all runnable programs are useful...
True indeed. You have to remember that this just a small example in a series for a talk I'm doing. The talk is entitled "Patters: Evolution" and is about how design patterns evolve into languages over time, and how programming languages influence one another. The Qi4j demo comes towards the end of a section starting with the axiom that any Turing complete language can be reimplemented with any other Turing complete language, moving on to writing object oriented C, then explaining the differences and similarities between OO-based and prototype based extension using Java script and Ruby. There are some mixin stuff and C# extension methods as well. This is where we get to Qi4j which has some similarities to the things shown earlier, even if its purpose is quite different. The context thing is something I need to look further into, but for now I'll stick to the code I've got because this is easier to trace back to the previous demos. Maybe I'll head over to Sweden and give the talk someday :-) Anders _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
