Dan Sugalski <[EMAIL PROTECTED]> wrote: > Okay, since I was asked, and I'm starting to hit a need for it in > general, I want to address morph, and some of its ramifications. And > limitations, as it seems like it's only a partial solution
The first question is: what are the supposed semantics of C<morph>? When and why should a HLL compiler emit C<morph>? > The easy out is to say that it's all PMC dependent and you should > just write the code to do what you want. That's the only possible way to go. Turning an IntvalArray into a PMCArray is a totally different thing then morphing a PerlInt into a PerlString. leo
