Bennett Todd <[EMAIL PROTECTED]> writes:
> I think the complaint about mod_perl's weight bears looking at, despite
> the success of the INN embedding. One invocation of INN is likely to do
> a sufficiently heroic amount of work that the weight and bulk of a perl
> in there may well not hurt a bit
2000-09-11-16:23:20 Dan Sugalski:
> At 03:16 PM 9/11/00 -0500, Jarkko Hietaniemi wrote:
> >On Mon, Sep 11, 2000 at 01:12:44PM -0700, Russ Allbery wrote:
> > > INN has been embedding Perl for years, quite successfully.
> >
> >There's embedding and there's embedding. Embedding in an UNIX server
> >
On Tue, Sep 12, 2000 at 04:55:02PM -0400, Dan Sugalski wrote:
> > Are there any better reasons than "It would be nice?"
> It'd make things easier? (I'd rather write a parser in perl than C...)
You're going to have to do it some time, for bootstrapping. And now you need
an interpreter on hand at t
On Tue, 12 Sep 2000, Simon Cozens wrote:
> On Tue, Sep 12, 2000 at 03:17:47PM -0400, Ken Fox wrote:
> > That's fine for the VM and the support libraries, but I'd *really* like
> > to see the parser/front-end in Perl. There are dozens of RFCs that require
> > some non-trivial extensions to the par
On Tue, Sep 12, 2000 at 03:17:47PM -0400, Ken Fox wrote:
> That's fine for the VM and the support libraries, but I'd *really* like
> to see the parser/front-end in Perl. There are dozens of RFCs that require
> some non-trivial extensions to the parser. It would be nice to code these
> in Perl
Are
"ye, wei" wrote:
> Tom Christiansen wrote:
> > It [miniperl] isn't substantially smaller, so that does you no good.
The socket library seems to be the poster child for what to leave
out, but that's a weak argument. If Perl 6 gets all the functionality
requested by Damian or the PDL folks, it woul
Dan Sugalski wrote:
> As for the language we implement perl in (and thus ultimately need to
> translate to the compiler-target language), I'm thinking of something like
> Chip's PIL.
That's fine for the VM and the support libraries, but I'd *really* like
to see the parser/front-end in Perl. There
At 03:57 PM 9/12/00 +0100, Leon Brocard wrote:
>Perl6 RFC Librarian sent the following bits through the ether:
>
> > Allow Perl to create serialize both data and code from the core.
>
>Hmmm, would it be enough to emit and take in bytecode? Might there be
>versions of Perl 6 which omit this functio
Dan Sugalski wrote:
> For something like:
>
>@foo = @bar || @baz;
>
> I have no problem with the call sequence looking like (pseudo-codish here):
>
> set_context(ARRAY, ASSIGN);
> foo->store(bar->log_or(bar, baz));
But log_or must short circuit -- I think we have to preserve that b
=head1 TITLE
Data/Binary Dumping and Freezing
=head1 VERSION
Maintainer: John van Vlaanderen
Date: 12 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 210
Version: 1
Status: Developing
=head1 ABSTRACT
Allow Perl to create serialize both data and code from the core.
Perl6 RFC Librarian sent the following bits through the ether:
> Allow Perl to create serialize both data and code from the core.
Hmmm, would it be enough to emit and take in bytecode? Might there be
versions of Perl 6 which omit this functionality?
As well as binary code, a human-readable vers
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Data/Binary Dumping and Freezing
=head1 VERSION
Maintainer: John van Vlaanderen
Date: 12 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 210
Version: 1
Status: Developing
=head1 ABSTRACT
A
12 matches
Mail list logo
