I'd appreciate comments, and if it's okay to commit it back to the
Can it remain as a separate module from PGE -- say, in
runtime/parrot/library/PGE/Hs.pir, rather than integrating it
directly into PGE.pbc? I don't have a big problem with adding
it to PGE.pbc if there's a good reason for doing it, but I'm trying
to keep the PGE core itself fairly lean and then use modules to
load in language-specific features. Even the expression dumper
is in a separate file (runtime/parrot/library/PGE/Dumper.pir).
Also, I'm not committed to PGE's current match."dump" format;
if the Haskell format makes more sense then perhaps we can
adopt it as the default. (I haven't tried it out yet to see
what it produces.)
If you really need it integrated with PGE itself we can do
Done as such. PGE-Hs.pbc now has to be built by hand, and the
default PGE.pbc no longer contains Hs.pir code.
Pugs will bundle PGE-Hs.pbc with it; it is good that parrot
won't built PGE-Hs.pbc by default, since that avoids version
clash (as parrot searches into library/ first, not ./).