On Sunday 01 April 2007 14:56, Steve Peters wrote:
> The attached patch are some of the cleanups needed for compiling Parrot
> with Borland C++ on Windows. It is not yet compiling after this patch
> because one of the changes that helped Borland C++ seems to cause the
> Parrot go out of control a
On 4/11/07, Bob Rogers <[EMAIL PROTECTED]> wrote:
I like this one, but I also have another alternative. First, make all
class-modification code (add_method, remove_attribute, etc) return a
PMC*. Whenever one of these methods is called on a class, the class
is cloned . . .
What does
# New Ticket Created by James Keenan
# Please include the string: [perl #42429]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42429 >
There are two points in docs/submission.pod where the word 'test' is
used is a way whi
From: "Alek Storm" <[EMAIL PROTECTED]>
Date: Wed, 11 Apr 2007 00:02:29 +
On 4/10/07, Allison Randal <[EMAIL PROTECTED]> wrote:
> 4) Do away with automatic morphing. Attempting to make changes to a
> class that's already been instantiated is not allowed (add_method, etc.
> wil
On 4/10/07, Allison Randal <[EMAIL PROTECTED]> wrote:
4) Do away with automatic morphing. Attempting to make changes to a
class that's already been instantiated is not allowed (add_method, etc.
will throw an exception). This also eliminates the need for
remove_method, remove_attribute, remove_rol
# New Ticket Created by Jerry Gay
# Please include the string: [perl #42427]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42427 >
i checked out parrot r18126, ran configure, and prove
t/codingstd/perlcritic.t. many tests
Am Mittwoch, 11. April 2007 00:25 schrieb Allison Randal:
> 3) Modify the core PMC implementation so it tracks information about
> which the different containers (registers, temporary variables,
> namespace entries, etc.) that hold a particular PMC, and which
> particular container was used to make
Jonathan raised a question in the #parrotsketch meeting today about our
strategy for safely changing classes that already have instantiated
objects. The core problem is this: when you create a class,
.local pmc classobj, object
classobj = newclass 'Foo'
instantiate an object from it,
ob
a week remains before the scheduled release of parrot 0.4.11. in this
time, the project team intends to focus on the implementation of
PDD15, objects. to that end, i've started a wiki page at
http://rakudo.org/parrot/index.cgi?pdd15_todo for folks to add items
for what remains un{specified,impleme
On 4/10/07, Steve Peters via RT <[EMAIL PROTECTED]> wrote:
I'll probably break apart this patch to get the enum fixes in and deal
with the larger STRING issue separately.
cohesive, loosely coupled patches are always preferred.
~jerry
On Mon Apr 09 23:01:35 2007, [EMAIL PROTECTED] wrote:
> On Sunday 08 April 2007 18:07, Steve Peters via RT wrote:
>
> > On Sun Apr 08 16:08:05 2007, stmpeters wrote:
> > > The attached patch includes several cleanups needed to silence
> > > warnings
> > > when compiling Parrot with Intel C++.
> >
This is the message I get while compiling parrot on linux :
./miniparrot config_lib.pasm > runtime/parrot/include/config.fpmc
real_exception (severity:2 error:30): Complex: malformed string
likely reason: argument count mismatch in main (more than 1 param)
make: *** [runtime/parrot/include/conf
# New Ticket Created by Joshua Isom
# Please include the string: [perl #42411]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42411 >
I recently got a new amd64 machine and worked on getting parrot
running, which was fairl
# New Ticket Created by "Alek Storm"
# Please include the string: [perl #42408]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42408 >
And... oops. Here's the patch, in all its glory.
--
Alek Storm
Index: src/objects.c
=
# New Ticket Created by Joshua Isom
# Please include the string: [perl #42412]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42412 >
Configure should act as though writing --foo=no is false instead of
true. Tonight I tri
# New Ticket Created by "Alek Storm"
# Please include the string: [perl #42407]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42407 >
This patch refactors and optimizes methods involved in vtable
overriding, eliminating se
jerry gay wrote:
On 4/9/07, Klaas-Jan Stol <[EMAIL PROTECTED]> wrote:
hi,
attached a patch that changes the file json.in. Currently, when doing
nmake test, it won't work (windows), as the changing to the test
directory and calling prove is separated by a ';'. This patch changes it
in &&.
I sen
# New Ticket Created by "Alek Storm"
# Please include the string: [perl #42406]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42406 >
This patch fixes the bug in which the "init" vtable method override is
called instead of
Joshua Isom wrote:
On Apr 10, 2007, at 2:05 AM, Allison Randal wrote:
Klaas-Jan Stol wrote:
hi,
Some suggestions for PDD15:
1.
reading PDD15, I noticed that some methods/ops are named using an
underscore to separate words, others don't, for instance:
* get_class (but also "getclass" is used
On Apr 10, 2007, at 2:05 AM, Allison Randal wrote:
Klaas-Jan Stol wrote:
hi,
Some suggestions for PDD15:
1.
reading PDD15, I noticed that some methods/ops are named using an
underscore to separate words, others don't, for instance:
* get_class (but also "getclass" is used in the examples)
* n
Jonathan Worthington wrote:
Hi,
In PDD15 we have both add and remove vtable methods for attributes,
parents and roles. However, we only have add_method. Was remove_method
missed out intentionally?
I was torn on remove_method. It makes sense from a consistency
perspective, but seems like ano
Author: allison
Date: Tue Apr 10 00:28:51 2007
New Revision: 18101
Modified:
trunk/docs/pdds/pdd15_objects.pod
Log:
[pdd]: Changes from latest round of comments: namespace method, remove_method,
get_class vs getclass.
Modified: trunk/docs/pdds/pdd15_objects.pod
==
Jonathan Worthington wrote:
Paul Cochrane (via RT) wrote:
In file src/ops/object.ops, in op callmethodcc(), there is the todo item:
"should we check if object.can(method)"
I think we should not need to do that; find_method will just hand back a
null PMC if it fails to find a method, and the
Jonathan Worthington wrote:
Hi,
Tonight I started working on the association between classes and
namespaces as specified in PDD15. Have some questions.
1) I added a "slot" to the NameSpace PMC to hold a Class or Role PMC a
while back. However, there is no interface specified for storing/gett
Klaas-Jan Stol wrote:
hi,
Some suggestions for PDD15:
1.
reading PDD15, I noticed that some methods/ops are named using an
underscore to separate words, others don't, for instance:
* get_class (but also "getclass" is used in the examples)
* newclass
IMO, it'd be nice to be consistent, and st
25 matches
Mail list logo
