Am 06.03.2014 01:13, schrieb Ingo W.:
This is a technical problem, but when you run into it, something is probably wrongly designed. And maybe one can simply solve it by programming against interfaces.
programming against interfaces works only if you (a) extract those, (b) solve the problems with interfaces that are supposed to be solved by inheritance, (c) forget about an inheritance in style of A-B-C, where B is written in your alternative JVM language.
The goal is to be able to freely mix languages. You cannot reach that by requiring to program against interfaces only. Well, not if you want to stay somehow OO
Programming against interfaces requires you to isolate the code parts written in the other JVM language.
bye Jochen -- Jochen "blackdrag" Theodorou - Groovy Project Tech Lead blog: http://blackdragsview.blogspot.com/ german groovy discussion newsgroup: de.comp.lang.misc For Groovy programming sources visit http://groovy-lang.org -- You received this message because you are subscribed to the Google Groups "JVM Languages" group. To unsubscribe from this group and stop receiving emails from it, send an email to jvm-languages+unsubscr...@googlegroups.com. To post to this group, send email to jvm-languages@googlegroups.com. Visit this group at http://groups.google.com/group/jvm-languages. For more options, visit https://groups.google.com/groups/opt_out.
