Re: [svn:parrot-pdd] r17312 - trunk/docs/pdds/draft

2007-03-04 Thread Sam Vilain
[EMAIL PROTECTED] wrote: > (When you extend an existing class, it actually creates > +a new class, that replaces the old class in the Namespace, but the old > +class can't be thrown away if it has objects instantiated in it. The old > +objects still point to the old class and do their method resolu

Re: AIX 5.3

2007-03-04 Thread Allison Randal
Theodore Katseres wrote: I managed to get parrot to build on aix-ppc-gcc4.0.0 smoked too ;) Excellent! :) Allison

[svn:parrot-pdd] r17321 - trunk/docs/pdds/draft

2007-03-04 Thread allison
Author: allison Date: Sun Mar 4 01:33:33 2007 New Revision: 17321 Modified: trunk/docs/pdds/draft/pdd15_objects.pod Log: [pdd]: Notes on container type in Objects PDD. Modified: trunk/docs/pdds/draft/pdd15_objects.pod =

[BUG]: Test failures in t/pmc/smop_attribute.t and t/pmc/smop_class.t

2007-03-04 Thread James Keenan
See attached output of prove -v. I have not encountered these failures before tonight. Updated to revision 17318. [parrot] 526 $ prove -v t/pmc/smop_*.t t/pmc/smop_attribute1..5 # Failed test (t/pmc/smop_attribute.t at line 26) # got: 'sh: line 1: ./parrot: No such file or dir

[svn:parrot-pdd] r17322 - trunk/docs/pdds/draft

2007-03-04 Thread jonathan
Author: jonathan Date: Sun Mar 4 02:19:10 2007 New Revision: 17322 Modified: trunk/docs/pdds/draft/pdd15_objects.pod Log: Describe new class and object layout for objects. We now push a lot into the class and make objects really lightweight, since you will usually instantiate many objects p

[svn:parrot-pdd] r17323 - trunk/docs/pdds/draft

2007-03-04 Thread allison
Author: allison Date: Sun Mar 4 02:30:36 2007 New Revision: 17323 Modified: trunk/docs/pdds/draft/pdd15_objects.pod Log: [pdd]: Objects, a few clarifications. Modified: trunk/docs/pdds/draft/pdd15_objects.pod == ---

Re: [perl #41583] Tail calls from within vtable methods broken

2007-03-04 Thread Jonathan Worthington
Bram Geron (via RT) wrote: Tail calls from within v-table methods are broken, the tail-called sub (or method) will not return correct values. When method A tailcalls sub B, B's set_returns stores its opcode number (and with it, which registers should be returned), but the low-level vtable code g

[svn:parrot-pdd] r17326 - trunk/docs/pdds/draft

2007-03-04 Thread allison
Author: allison Date: Sun Mar 4 03:40:00 2007 New Revision: 17326 Modified: trunk/docs/pdds/draft/pdd15_objects.pod Log: [pdd]: Review of updates from 2am design session on object structures. Modified: trunk/docs/pdds/draft/pdd15_objects.pod =

Re: [svn:parrot-pdd] r17312 - trunk/docs/pdds/draft

2007-03-04 Thread Allison Randal
Sam Vilain wrote: Is it intended that if languages need to make changes to the behaviour of existing obejcts through their type, that something may follow up after this and replace the old objects with objects of the new type? Yes. Some languages will want that behavior, and some won't, so Par

Parrot won't build on cygwin

2007-03-04 Thread Klaas-Jan Stol
hi, I'm trying to compile parrot on cygwin, but it won't compile: mpilers/imcc/parser_util.o compilers/imcc/pcc.o -lcrypt -lgmp -lreadline compilers/imcc/main.c /usr/bin/perl.exe tools/build/parrot_config_c.pl --mini > \ src/null_config.c src/null_config.c gcc -o miniparrot.exe compilers

[svn:parrot-pdd] r17322 - trunk/docs/pdds/draft

2007-03-04 Thread Bob Rogers
From: [EMAIL PROTECTED] Date: Sun, 4 Mar 2007 02:19:16 -0800 (PST) Author: jonathan Date: Sun Mar 4 02:19:10 2007 New Revision: 17322 Modified: trunk/docs/pdds/draft/pdd15_objects.pod . . . Modified: trunk/docs/pdds/draft/pdd15_objects.pod ===

[perl #41695] [CAGE]: Refactor Parrot::Distribution

2007-03-04 Thread via RT
# New Ticket Created by James Keenan # Please include the string: [perl #41695] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41695 > I am opening this ticket as a way of logging various Parrot hackers' efforts to re-fac

[perl #41693] [PATCH] STM article reference corrected

2007-03-04 Thread via RT
# New Ticket Created by Elizabeth Mattijsen # Please include the string: [perl #41693] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41693 > Robert Ennals' paper doesn't live at the indicated link anymore, even his own we

[perl #41693] [PATCH] STM article reference corrected

2007-03-04 Thread Bob Rogers
From: Elizabeth Mattijsen (via RT) <[EMAIL PROTECTED]> Date: Sun, 04 Mar 2007 05:15:43 -0800 # New Ticket Created by Elizabeth Mattijsen # Please include the string: [perl #41693] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ti

Re: AIX 5.3

2007-03-04 Thread jerry gay
On 3/3/07, Theodore Katseres <[EMAIL PROTECTED]> wrote: I managed to get parrot to build on aix-ppc-gcc4.0.0 smoked too ;) indeed, wonderful news. is this something that can be set up more regularly so we can track portability there? also, i can't seem to find the smoke results at http://smoke

Re: [perl #41602] [TODO] MS VS 2005 deprecates strdup

2007-03-04 Thread Klaas-Jan Stol
[EMAIL PROTECTED] via RT wrote: Hi, Applied in 17281, thanks. For your question, strdup is fine since these are not garbage collectable strings (STRING*), just normal C char*'s. There is loads of them used in IMCC. Unfortunately though, there is an issue in that we don't free a load of 'em, or

Re: [perl #41619] [PATCH] add add_attr, rem_attr, and rem_attr_str vtable methods

2007-03-04 Thread Alek Storm
For the same reason we have set_attr, set_attr_str, get_attr, and get_attr_str, even though they're only used by ParrotObject - it allows for multiple, concurrent object systems. This goal is mentioned in PDD 15, in "What The Bytecode Sees". Why tie programmers into the default way of doing thin

Re: [perl #41583] Tail calls from within vtable methods broken

2007-03-04 Thread Alek Storm
I'm almost done with a different patch that preserves the parent context for the purpose of returning values into it. All further tailcalled contexts are freed as normal. That's pretty vague, but it's easier just to see the code. I just haven't had time to finish and release it. Thanks, Alek S

Re: [perl #41364] [PATCH] Fixed object vtable method overrides in PIR

2007-03-04 Thread Alek Storm
That's because the patch refers to a function that is now outdated because of #41549. I've attached an updated version of the patch. Thanks, Alek Storm On 3/2/07, [EMAIL PROTECTED] via RT <[EMAIL PROTECTED]> wrote: On Sun Feb 25 20:10:00 2007, [EMAIL PROTECTED] wrote: > Now that 0.4.9 has bee

[perl #41695] [CAGE]: Refactor Parrot::Distribution

2007-03-04 Thread James Keenan via RT
Here are some notes which I have made which may prove useful in the refactoring of Parrot::Distribution. I hope that I have grepped and acked accurately, but I'm not guaranteeing 100% accuracy. kid51 NAME Parrot::Distribution refactoring notes ANALYSIS OF PACKAGE * used by: *

Re: [perl #41619] [PATCH] add add_attr, rem_attr, and rem_attr_str vtable methods

2007-03-04 Thread Joshua Isom
On Mar 4, 2007, at 12:40 PM, Alek Storm wrote: For the same reason we have set_attr, set_attr_str, get_attr, and get_attr_str, even though they're only used by ParrotObject - it allows for multiple, concurrent object systems. This goal is mentioned in PDD 15, in "What The Bytecode Sees". Why

Re: [PATCH]: tools for using Subversion branches; ops2c.pl refactored

2007-03-04 Thread Sam Vilain
James Keenan wrote: > The patch attached is really two patches in one: > > 1. A resubmission in patch form of my refactoring of tools/build/ > ops2c.pl into lib/Parrot/Ops2c/Utils.pm and lib/Parrot/Ops2c/ > Auxiliary.pm, along with a test suite in t/tools/ops2cutils/. > > 2. 4 new files which p

[svn:parrot-pdd] r17336 - trunk/docs/pdds/draft

2007-03-04 Thread jonathan
Author: jonathan Date: Sun Mar 4 14:47:00 2007 New Revision: 17336 Modified: trunk/docs/pdds/draft/pdd15_objects.pod Log: s/variable/value/ - bob rogers++ Modified: trunk/docs/pdds/draft/pdd15_objects.pod == --- trun

Re: [PATCH]: tools for using Subversion branches; ops2c.pl refactored

2007-03-04 Thread James Keenan
On Mar 4, 2007, at 5:15 PM, Sam Vilain wrote: James Keenan wrote: The patch attached is really two patches in one: 1. A resubmission in patch form of my refactoring of tools/build/ ops2c.pl into lib/Parrot/Ops2c/Utils.pm and lib/Parrot/Ops2c/ Auxiliary.pm, along with a test suite in t/tools/

Re: [PATCH]: tools for using Subversion branches; ops2c.pl refactored

2007-03-04 Thread Sam Vilain
James Keenan wrote: >> Why are these two changes tied together? Surely if you have a capable >> feature branching system this is not necessary. > I submitted individual patches and new files last week for the > refactoring of ops2c.pl. Following the instructions in docs/ > submission.pod, I ed

Re: [PATCH]: tools for using Subversion branches; ops2c.pl refactored

2007-03-04 Thread chromatic
On Sunday 04 March 2007 15:41, Sam Vilain wrote: > James Keenan wrote: > > Those patches and new files haven't been reviewed yet.  When I went   > > to my next round of submissions, I wanted to get it done quickly   > > (I've been dealing with eye infections the last several days and am   > > tir

Re: [PATCH]: tools for using Subversion branches; ops2c.pl refactored

2007-03-04 Thread Sam Vilain
chromatic wrote: >> Mixing things together is everything that you are attempting to resolve. >> Why are you making excuses for not achieving this? >> > > I don't think that's entirely fair. James's experiment here is an > experiment, > and if it fails we can learn something from it. > Y

Re: [perl #41619] [PATCH] add add_attr, rem_attr, and rem_attr_str vtable methods

2007-03-04 Thread Alek Storm
The same questions are solved for all PMCs - the vtable provides an abstracted interface that everyone can use seamlessly. Because tcl and Java use the same interface (opcodes), there's no problem. I honestly cannot see a difference between these and any other vtable method. The fact that Perl

Re: [perl #41619] [PATCH] add add_attr, rem_attr, and rem_attr_str vtable methods

2007-03-04 Thread chromatic
On Sunday 04 March 2007 19:13, Alek Storm wrote: > In fact, these vtable methods *encourage* the use of many languages in > a single application. For example, without these methods, programmers > have to be aware of the semantics of the Smalltalk object system and > use extra code when dealing wi

Re: [perl #41364] [PATCH] Fixed object vtable method overrides in PIR

2007-03-04 Thread Alek Storm
Just kidding! Here's the patch, for real this time. On 3/4/07, Alek Storm <[EMAIL PROTECTED]> wrote: That's because the patch refers to a function that is now outdated because of #41549. I've attached an updated version of the patch. Thanks, Alek Storm On 3/2/07, [EMAIL PROTECTED] via RT <[E

Re: [perl #41619] [PATCH] add add_attr, rem_attr, and rem_attr_str vtable methods

2007-03-04 Thread Alek Storm
Hmm, no, these deal with normal object attributes. I believe you're thinking of properties. I'll put together some sketch code with what I already have and post that. Thanks, Alek Storm On 3/5/07, chromatic <[EMAIL PROTECTED]> wrote: On Sunday 04 March 2007 19:13, Alek Storm wrote: > In fact