Chip Salzenberg <chip@valinux.com> writes: >According to Nick Ing-Simmons: >> Chip's pre-C++ mechanism was to use "PI" (Perl Implementation >> language) Chip then went on to say this is because he "hates >> embed.pl". > >Actually, Nick, I think you misunderstood. PI still exists and is >still a possible part of the Perl 6 puzzle, but it doesn't solve the >embedding problem. It just solves the *inheritance* problem. ... > >I consider something like 'embed.pl' to be a necessary price to pay >for using a language as low-level as C for tasks like embedding. I think you misunderstood too - not hard as you were still packing up when we had discussion ;-) Given that PI (or whatever) is writing out the to-be-cc-ed C code adding a bit here and there; it may as well s/foo/PL_foo/ or even s/foo/(*(*PLinterp->vtable.foo()))/ or whatever the current flavour of the month is for the result off CPPing with generated embed.h. Then there is no CPP messiness in the C code so no name clashes. Think of it as a bit like C-front C++ compiler. -- Nick Ing-Simmons