On Thu, Nov 14, 2002 at 03:09:54PM +0530, Gopal V wrote: > Also perl6c.pbc shouldn't really worry about trojaned stuff in it as you're > not using an external bootstrapper (unlike gcc using cc)....
I don't think you're totally correct. You are still relying on an external bootstrapper, although it's from a source you (think you) trust - the parrot distribution. If someone cracks the parrot distribution's server, and installs a trojaned perl6c.pbc that contains extra routines to recognise when it is compiling perl6c.pl, then the running perl6 compiler could interest its extra routines into the bytecode of the perl6 compiler. And again next generation. And again next ... In the same way that the self-replication code for cc worked. Nicholas Clark
