Dan wrote: > I was hoping we'd see hybrid PMCs -- that is, language specific > PMCs that were fully implemented both in pure bytecode and in C.
Huh? Parallel maintenance of duplicate complex implementations? On _purpose_? "That trick *never* works!" > I'd like to see parrot include a set of core PMCs that implement fairly > pure abstractions, without any language-specific stuff (such as > automatic conversions, preconceived notions of which string values are > true/false etc). Well, we're going to (continue to) have string<->integer and string<->double conversions built in, because integer, double, and string registers are built in; they're fundamental VM concepts for Parrot. String true/false value, though, I agree; Parrot core PMCs and opcodes shouldn't have any opinion on that. -- Chip Salzenberg <[EMAIL PROTECTED]>
