Hi Affijn, As I gradually learn how Parrot works, I see that perhaps the idea of decompiling byte-code into language ___ is only a pipe-dream. But the point still remains--using the fact that one *could* mix languages X, Y, and P into your company's source tree is a very weak argument for Parrot/Perl6. I would say it is a non-argument.
As you point out, it can already be done with Inline.pm & friends. In fact, it can be done even more blatantly with backticks. It has long been possible to do stuff like this: #!perl5 $a = `/usr/bin/java foo.class`; $b = `/usr/bin/php bar.php`; $c = $a + b; The reason this would make an IT Manager cry is not (promarily) because it is slow (etc, etc), it also means she now has to keep a Java/PHP/Perl programmer around and happy whenever one of three different languages might throw a buggie. --michael On 26/05/06, Dr.Ruud <[EMAIL PROTECTED]> wrote: