Re: Is Parrot 1.0 too late?

2007-04-24 Thread Joshua Juran
On Apr 24, 2007, at 11:21 PM, chromatic wrote: On Tuesday 24 April 2007 15:31, Nikolay Ananiev wrote: Why would the developers use Parrot instead of JVM/CLR/Mono? Parrot is open source today, not *mumble* down the road like the JVM will be. Parrot is also widely portable, much like perl

Re: Is Parrot 1.0 too late?

2007-04-24 Thread chromatic
On Tuesday 24 April 2007 15:31, Nikolay Ananiev wrote: > Why would the developers use Parrot instead of JVM/CLR/Mono? Parrot is open source today, not *mumble* down the road like the JVM will be. Parrot supports more dynamic features than only "find method by name at runtime". Parrot doesn't h

Re: Is Parrot 1.0 too late?

2007-04-24 Thread Allison Randal
Nikolay Ananiev wrote: So, is one of parrot's biggest strengths gone? Are we too late? Why would the developers use Parrot instead of JVM/CLR/Mono? We're certainly pleased that we kicked off a revolution in virtual machines, and that others are beginning to catch on to the fact that they'll

Re: My brain dump for the PMCs PDD

2007-04-24 Thread Allison Randal
Leopold Toetsch wrote: This is what the cstruct-Proposal is for. The cstruct is describing the internals of a PMC (which happen to consist of C structure items) Aye. For general information, these are the current draft PDDs that I'm merging into 1 (or 2) PMC PDDs. pdd02_vtables.pod pdd04_d

Is Parrot 1.0 too late?

2007-04-24 Thread Nikolay Ananiev
As we all know, parrot has been in development for 7 years now. That's a lot of time and many things have changed since then. From my point of view one of the biggest strengths of Parrot is that it's a target for many (and why not all?) dynamic languages and as I know there's no other VM like it.

Re: [perl #42620] PGE 'Out of memory' panics.

2007-04-24 Thread Patrick R. Michaud
On Tue, Apr 24, 2007 at 04:30:53PM -0400, Andy Dougherty wrote: > On Tue, 24 Apr 2007, Patrick R. Michaud wrote: > > With chromatic's patch in r18323 (RT #42320), and removing the -G > > flag from the relevant files, I'm now able to run PGE's tests > > including p5rx.t and 01-regex.t in under 60MB

Re: [perl #42620] PGE 'Out of memory' panics.

2007-04-24 Thread chromatic
On Tuesday 24 April 2007 13:30, Andy Dougherty wrote: > > Andy, could you update to r18323, remove the -G's, and see if it > > now runs to completion on your Solaris box? > Thanks for the heads-up. I'm afraid testing will have to wait until > tomorrow. The rsync server at svn.perl.org is still

Re: [perl #42620] PGE 'Out of memory' panics.

2007-04-24 Thread Andy Dougherty
On Tue, 24 Apr 2007, Patrick R. Michaud wrote: > With chromatic's patch in r18323 (RT #42320), and removing the -G > flag from the relevant files, I'm now able to run PGE's tests > including p5rx.t and 01-regex.t in under 60MB of virtual > memory. (See below.) > > Andy, could you update to r183

Re: [perl #42620] PGE 'Out of memory' panics.

2007-04-24 Thread Patrick R. Michaud
On Fri, Apr 20, 2007 at 03:52:35PM -0400, Andy Dougherty wrote: > Oh yes. It's swapping like crazy. Sorry I didn't mention that > explicitly. (I figured it was obvious!) The machine in question has > 128 MB of physical RAM. [...] > > Specifically, I usually do something like: > > ulimi

Re: My brain dump for the PMCs PDD

2007-04-24 Thread Leopold Toetsch
Am Montag, 23. April 2007 23:18 schrieb Jonathan Worthington: > Proposal: PMCs can have attributes just as classes in HLLs have > attributes. This is somewhat related to variable sized PMCs; note you > can leave PMC headers fixed size and just have a pmc_ext like structure > that is the variable si

Re: [perl #42320] [BUG] Memory leak with String pmc

2007-04-24 Thread Leopold Toetsch
Am Dienstag, 24. April 2007 07:45 schrieb chromatic: > Here's my solution; don't allocate zero-sized buffers.  Let them be empty. Great catch. Thanks. Indeed - zero-size allocs should just be ignored or/and even the source of such requests be weeded out. leo

[perl #42407] [PATCH] refactor vtable overriding, delegate.c generation

2007-04-24 Thread Matt Diephouse via RT
On Mon Apr 23 13:39:40 2007, [EMAIL PROTECTED] wrote: > Gracias. I attached one more small patch that gets rid of two > seemingly unnecessary lines in smop_init() - they're easy to miss when > one's looking at the big picture. Applied in r18321. Thanks! -- Matt Diephouse

Re: [perl #42699] r18304 Test failures on NexentaOS (GNU/OpenSolaris)

2007-04-24 Thread Alek Storm
On 4/24/07, via RT Ron Blaschke <[EMAIL PROTECTED]> wrote: The output of the failed tests is attached. No, it's not. One more time, with feeling ;). -- Alek Storm

Re: [perl #42692] install error with output

2007-04-24 Thread [EMAIL PROTECTED]
FIRST STEP: [EMAIL PROTECTED] ~/parrot $ perl Configure.pl Parrot Version 0.4.11 Configure 2.0 Copyright (C) 2001-2007, The Perl Foundation. Hello, I'm Configure. My job is to poke and prod your system to figure out how to build Parrot. The process is completely automated, unless you passed i

[perl #42699] r18304 Test failures on NexentaOS (GNU/OpenSolaris)

2007-04-24 Thread via RT
# New Ticket Created by Ron Blaschke # Please include the string: [perl #42699] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=42699 > This is a follow up for ticket #42587, using Parrot r18304. SunOS nexenta 5.11 NexentaO