[PATCH] PGE::Hs for Pugs PGE support

1 view
Skip to first unread message

Autrijus Tang

unread,
May 8, 2005, 7:24:49 PM5/8/05
to Patrick R. Michaud, perl6-i...@perl.org
Greetings. Attached is a patch that I'm currently using in Pugs's
bundled PGE.pbc, in order to make PGE output properly escaped strings,
in a format ready to be used form Haskell FFI.

I'd appreciate comments, and if it's okay to commit it back to the
PGE directory.

Thanks,
/Autrijus/

pge-hs.patch

Patrick R. Michaud

unread,
May 8, 2005, 11:25:43 PM5/8/05
to Autrijus Tang, perl6-i...@perl.org

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
that.

Pm

Autrijus Tang

unread,
May 10, 2005, 12:19:58 AM5/10/05
to Patrick R. Michaud, Autrijus Tang, perl6-i...@perl.org
On Sun, May 08, 2005 at 10:25:43PM -0500, Patrick R. Michaud wrote:
> On Mon, May 09, 2005 at 07:24:49AM +0800, Autrijus Tang wrote:
> > Greetings. Attached is a patch that I'm currently using in Pugs's
> > bundled PGE.pbc, in order to make PGE output properly escaped strings,
> > in a format ready to be used form Haskell FFI.
> >
> > I'd appreciate comments, and if it's okay to commit it back to the
> > PGE directory.
>
> 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.

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 ./).

Thanks!
/Autrijus/

Reply all
Reply to author
Forward
0 new messages