Tim Bunce <[EMAIL PROTECTED]> writes:
> On Tue, Jun 25, 2002 at 11:35:20AM +0100, Dave Mitchell wrote:
>> On Tue, Jun 25, 2002 at 11:08:53AM +0100, Tim Bunce wrote:
>> > On Tue, Jun 25, 2002 at 12:23:34AM +0100, Dave Mitchell wrote:
>> > > Of course, another approach is to embed the existing Perl
On Tue, Jun 25, 2002 at 05:17:56PM +0100, Dave Mitchell wrote:
> On Tue, Jun 25, 2002 at 04:45:37PM +0100, Tim Bunce wrote:
> > On Tue, Jun 25, 2002 at 11:35:20AM +0100, Dave Mitchell wrote:
> > > On Tue, Jun 25, 2002 at 11:08:53AM +0100, Tim Bunce wrote:
> > > > On Tue, Jun 25, 2002 at 12:23:34AM
On Tue, Jun 25, 2002 at 04:45:37PM +0100, Tim Bunce wrote:
> On Tue, Jun 25, 2002 at 11:35:20AM +0100, Dave Mitchell wrote:
> > On Tue, Jun 25, 2002 at 11:08:53AM +0100, Tim Bunce wrote:
> > > On Tue, Jun 25, 2002 at 12:23:34AM +0100, Dave Mitchell wrote:
> > > > Of course, another approach is to
On Tue, Jun 25, 2002 at 11:35:20AM +0100, Dave Mitchell wrote:
> On Tue, Jun 25, 2002 at 11:08:53AM +0100, Tim Bunce wrote:
> > On Tue, Jun 25, 2002 at 12:23:34AM +0100, Dave Mitchell wrote:
> > > Of course, another approach is to embed the existing Perl5 interpreter
> > > within the Perl 6 interp
On Mon, Jun 24, 2002 at 05:58:23PM -0500, Dan Sugalski wrote:
> At 9:50 PM +0100 6/23/02, Tim Bunce wrote:
> >On Mon, Jun 17, 2002 at 07:59:33PM -0400, David J. Goehrig wrote:
> >>
> >> qw/ who is praying for parrot to support XS code,
> >>cause he doesn't want to rewrite
> >>SDL_perl's 1
At 9:50 PM +0100 6/23/02, Tim Bunce wrote:
>On Mon, Jun 17, 2002 at 07:59:33PM -0400, David J. Goehrig wrote:
>>
>> qw/ who is praying for parrot to support XS code,
>> cause he doesn't want to rewrite
>> SDL_perl's 11,000 lines /;
>
>I'm sure that's not going to happen.
>
>Much more li
On Tue, Jun 25, 2002 at 11:08:53AM +0100, Tim Bunce wrote:
> On Tue, Jun 25, 2002 at 12:23:34AM +0100, Dave Mitchell wrote:
> > Of course, another approach is to embed the existing Perl5 interpreter
> > within the Perl 6 interpreter; Perl6 subs call glue which calls Perl subs
> > which calls perl5
On Tue, Jun 25, 2002 at 12:23:34AM +0100, Dave Mitchell wrote:
> On Mon, Jun 24, 2002 at 05:21:45PM -0400, David J. Goehrig wrote:
> > On Sun, Jun 23, 2002 at 09:50:02PM +0100, Tim Bunce wrote:
> > > Much more likely is some kind of wrapper that manages a simple
> > > perl5-like run-time environme
On Mon, Jun 24, 2002 at 05:21:45PM -0400, David J. Goehrig wrote:
> On Sun, Jun 23, 2002 at 09:50:02PM +0100, Tim Bunce wrote:
> > Much more likely is some kind of wrapper that manages a simple
> > perl5-like run-time environment (stacks, marks, gimme, symboltable
> > etc) plus source-code compati
On Sun, Jun 23, 2002 at 09:50:02PM +0100, Tim Bunce wrote:
> Much more likely is some kind of wrapper that manages a simple
> perl5-like run-time environment (stacks, marks, gimme, symboltable
> etc) plus source-code compatibility support (macros, functions etc)
> that's just sufficient to keep ol
On Mon, Jun 17, 2002 at 07:59:33PM -0400, David J. Goehrig wrote:
>
> qw/ who is praying for parrot to support XS code,
> cause he doesn't want to rewrite
> SDL_perl's 11,000 lines /;
I'm sure that's not going to happen.
Much more likely is some kind of wrapper that manages a simpl
Hey stop bad mouthing macros :)
5's problems with macros is not that there are so many of them, but that documentation
and usage guidelines are hard to come by. The lesson, for Parrot developers to learn
from 5's macros, is that both macros and functions, the entire internal API, must
be doc
12 matches
Mail list logo
