On behalf of the Parrot team, I'm proud to announce Parrot 0.7.1
"Manu Aloha." Parrot (http://parrotcode.org/) is a virtual machine aimed
at running all dynamic languages.
Parrot 0.7.1 is available via CPAN (soon), or follow the download
instructions at http://parrotcode.org/source.html . For tho
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #58946]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58946 >
This metaticket is for issues related to the October 2008 release of
Parrot, plann
On Tue, Sep 16, 2008 at 11:45:17PM +0200, Allison Randal wrote:
> Patrick R. Michaud wrote:
> What's TAKE?
TAKE is like CONTROL_RETURN except that it signals that we expect
execution to continue after the point of the TAKE. It's quite
similar to a .yield operation for coroutines
From: Allison Randal <[EMAIL PROTECTED]>
Date: Tue, 16 Sep 2008 22:51:29 +0200
Yes, once we have the ability to have exception handlers only handle
specific types of exceptions, then they'll allow all other types of
exceptions to pass through. (Which means we won't end up with the
Daniel Ruoso daniel-at-ruoso.com |Perl 6| wrote:
For an Object to be a value, it means that if you build an object with
the same "value", it will be seen as the same "value" that some other
object with this value.
Perl 6 formalizes this by defining a "value type" as one whose identity
is key
TSa Thomas.Sandlass-at-vts-systems.de |Perl 6| wrote:
I think that mutating methods of immutable value types just have
to modify the identity. The problem is how that relates to references.
Take e.g. the Str type
my $s = 'abc'; # $s points to 'abc'
$s.reverse;
where the reverse method re
Stéphane Payrard cognominal-at-gmail.com |Perl 6| wrote:
I don't understand how = differs with that semantic from :=
I would expect that = would make a copy (clone?) of the object.
For a mutable object, I don't know if that copy should be immediate or deffered
by a mechanism of copy on write. Pro
On Tue Sep 16 15:45:47 2008, [EMAIL PROTECTED] wrote:
>
> Okay, here's what I propose we do:
>
> 1. I will examine the 12 unresolved tickets to see if there are any
> which will not be automatically closable once my patch is applied.
>
Examination complete.
> 2. I will apply a refined versio
As the discussion evolved in RT 58742, the consensus was that the
current smartlink functionality in Parrot is not working and that a
fresh approach must be taken. So we're deleting the smartlink-related
files (or, at the very least, those outside of the languages/
directory). That means we can t
Rejected, as we're deleting the file proposed for expansion.
Rejected, as we're deleting this file.
Rejected, as we're deleting the file proposed for expansion.
Rejected, as we're deleting the file proposed for expansion.
Rejected, as we're deleting the file proposed for expansion.
Rejected, as we're deleting the file proposed for expansion.
Rejected, as we're deleting the file proposed for expansion.
Rejected, as we're deleting the file proposed for expansion.
Rejected, as we're deleting the file proposed for expansion.
Rejected, as we're deleting the test file which the OP calls for expanding.
Rejected, as we're deleting the test file which the OP calls for expanding.
On Tue Sep 16 06:50:26 2008, particle wrote:
> >
> parrot needs a way for us to measure spec coverage in our test suite.
> i started the current smartlinks code as an experiment in using moose,
> and as a reaction to the mess of smartlink code that's in the pugs
> repo. however, i'm not married to
Marked as rejected.
Christoph Otto via RT wrote:
On Mon Oct 22 07:01:59 2007, pcoch wrote:
In src/pmc/hash.pmc:thaw() there is the todo item:
/* TODO make a better interface for hash creation
... do this.
Where do we want to go with this?
Ax the ticket. Vague plans for future change aren't useful.
Allison
On Tuesday 16 September 2008 14:47:58 NotFound wrote:
> > It certainly shouldn't segfault. But, the question is: why does it
> > segfault at 206 parameters? Throwing an exception to avoid an error we
> > don't understand isn't good for the long-term health of the VM.
>
> The problem is located ins
On Tue, Sep 16, 2008 at 11:55:25AM -0700, P N wrote:
> HI
>
>
>
> sorry to bug you - but I'm getting this message from you and others quite
> often.
>
> how would I un-subsscribe to this. If you knew how, please let me know.
Mailing [EMAIL PROTECTED] should work.
(assuming that that's the li
Vasily Chekalkin wrote:
And another question. Should all lvalue occurences of PMC_*_val(SELF) be
replaced with VTABLE_set_*_native? (Except for VTABLE method
implementation of cause)
In general, yes. You'll have to check each PMC to see if they have the
appropriate VTABLE_set_*(_native) vta
On Tue, Sep 16, 2008 at 12:27 PM, via RT Moritz Lenz
<[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Moritz Lenz
> # Please include the string: [perl #58934]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=58934 >
>
>
>
> It certainly shouldn't segfault. But, the question is: why does it segfault
> at 206 parameters? Throwing an exception to avoid an error we don't
> understand isn't good for the long-term health of the VM.
The problem is located inside compilers/imcc/pcc.c:pcc_get_args function.
It has the comm
Patrick R. Michaud wrote:
On Sat, Sep 13, 2008 at 01:55:05PM -0400, Will Coleda wrote:
+CONTROL_TAKE
} exception_type_enum;
Tcl can currently deal with OK, CONTINUE, BREAK, ERROR, and RETURN.
What's TAKE?
TAKE is like CONTROL_RETURN except that it signals that we expect
execution to
# New Ticket Created by Moritz Lenz
# Please include the string: [perl #58934]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58934 >
'make fulltest' runs several chunks of tests, and does not show a final
summary. So altho
Ter, 2008-09-16 às 18:04 +0200, TSa escreveu:
> I think that mutating methods of immutable value types just have
> to modify the identity. The problem is how that relates to references.
> Take e.g. the Str type
I really think we are looking at this problem from the wrong
perspective.
For an Objec
HI
sorry to bug you - but I'm getting this message from you and others quite often.
how would I un-subsscribe to this. If you knew how, please let me know.
thanks
Peter.
[EMAIL PROTECTED]
Peter.
[EMAIL PROTECTED]
--- On Tue, 9/16/08, Stephen Simmons <[EMAIL PROTECTED]> wrote:
From: Ste
Reini Urban (via RT) wrote:
Old: Guess extensions, so that the user can drop the extensions
leaving it up to the build process/install whether or not
a .pbc, .pasm, .past or a .pir file is used.
New: Search only for .pbc, .pasm, and .pir in that order.
The .past file-extension is *long* depreca
NotFound wrote:
By the way, as mentioned in other thread there is a problem with plain
%s in parrot printf-alike functions. It does not handle well a NULL c
string. This must be fixed. And before, given the current
implementation, the behavior of string_make and his successor in the
strings pdd,
Klaas-Jan Stol wrote:
Allison:
I made the following changes in pirc/new:
.arg -> .set_arg
.result -> .get_result
.return -> .tailcall (in context of .return foo() , which thus is now:
.tailcall foo() )
.return -> .set_return (in long-style returning : .begin/end_return
.yield -> .set_yield ( in
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #58936]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58936 >
With Rakudo 0.7.0-devel r31065 inheritance works as in this
single file:
class
# New Ticket Created by Stephane Payrard
# Please include the string: [perl #58924]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58924 >
It prints "0\n" instead of the expected "i\n"
--
cognominal stef
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #58922]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58922 >
Calling .perl on a self-referent structure makes Rakudo r31152 hang.
$ ./perl6 -e 'my @
Klaas-Jan Stol wrote:
This ticket doesn't seem to be closeable as is.Would it be good enough
if pmc2c.pl spit out an error on the above definition, or is this even
something that pmc2c.pl should be concerned about?
The goal of the ticket should be for pmc2c.pl to entirely parse the
input PMC fi
2008/9/16 via RT Reini Urban <[EMAIL PROTECTED]>:
> # http://rt.perl.org/rt3/Ticket/Display.html?id=58938 >
If you don't spot the error immediately, here's a hint:
> #5 0x639518e0 in pmc_type () from /usr/bin/cygparrot0_7_0.dll
wrong lib. caused by what?
the lib should be called
/usr/src/parrot/
Stephen Weeks wrote:
ExceptionHandler currently has a can_handle method that checks whether
the EH has been disabled or not. I propose adding some attributes to
store the minimum severity the EH will handle and the list of exception
types the EH will handle, methods to set and get these properti
# New Ticket Created by Reini Urban
# Please include the string: [perl #58938]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58938 >
Since a few days loadlib initialization causes an
src/string.c:2241: failed assertion '(s
On Tue, Sep 16, 2008 at 10:14:24PM +0200, Allison Randal wrote:
>
> Okay, PDD cleaned up. The code to directly support throwing any
> arbitrary type would require significant circumlocution (read:
> inefficient, difficult to maintain), so it's not desirable.
> [...]
> But, an individual HLL ca
Christoph Otto (via RT) wrote:
I was looking at #45357 ([TODO] Which exception should be thrown with register
overflow?) and found that Parrot doesn't like subs with more than 205 params.
This seems like a perfectly reasonable limit, but perhaps the behavior could
be more user-friendly.* M
Will Coleda (via RT) wrote:
[...]
I would expect one of the following things to happen here, either:
- an error is generated when test2 is parsed because there is no name
for the named parameter, or
- test2's blarg .param should default to being named 'blarg', so both
calls should work identica
Patrick R. Michaud wrote:
PDD23:67 has:
: =item B>
:
: Throw an exception consisting of the given I PMC. Active exception
: handlers (if any) will be invoked with I as the only parameter.
:
:
: =item B [ , I ]>
:
: Throw an exception consisting of the given I PMC after taking
: a continua
Author: allison
Date: Tue Sep 16 13:12:27 2008
New Revision: 31186
Modified:
trunk/docs/pdds/pdd23_exceptions.pod
Log:
[pdd] Clarifying the description of the 'throw' opcode, and the necessary
interface of thrown exceptions.
Modified: trunk/docs/pdds/pdd23_exceptions.pod
I think you've gone about this in the right way, but need to handle the
various cases a bit more broadly. Specifically, you can't assume that
everyone has strerror() at all (Solaris 8 doesn't, for example) nor that
everyone who uses int strerror_r() will also define either _XOPEN_SOURCE
or _PO
On Tue, Sep 16, 2008 at 06:11:30PM +0200, Moritz Lenz wrote:
> Stephen Simmons (via RT) wrote:
> > sub max($a, $b) {
> > if defined $a && defined $b {
> > if $a >= $b { return $a } else { return $b }
> > }
> > elsif defined $a { return $a }
> > elsif defined $b { return
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #58932]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58932 >
Sometime after the 0.7.1 release, the P6object library will change
so that double-
TSa wrote:
> HaloO,
>
> Darren Duncan wrote:
>> If you are wanting to actually mutate a Dog in a user-visible way rather
>> than deriving another Dog, then I don't think that calling Dog a value
>> type is appropriate.
>
> I think that mutating methods of immutable value types just have
> to mo
Stephen Simmons (via RT) wrote:
> # New Ticket Created by Stephen Simmons
> # Please include the string: [perl #58282]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=58282 >
>
>
> I wrote a two argument max function, wh
HaloO,
Darren Duncan wrote:
If you are wanting to actually mutate a Dog in a user-visible way rather
than deriving another Dog, then I don't think that calling Dog a value
type is appropriate.
I think that mutating methods of immutable value types just have
to modify the identity. The problem
chromatic via RT wrote:
On Monday 15 September 2008 23:21:26 Christoph Otto wrote:
--- src/pmc/os.pmc (revision 31173)
+++ src/pmc/os.pmc (working copy)
@@ -31,9 +31,6 @@
#include "parrot/parrot.h"
-/* XXX Check if we need to deallocate strerror strings */
-/* XXX apparently, strer
On Tue, Sep 16, 2008 at 4:26 AM, Stéphane Payrard <[EMAIL PROTECTED]> wrote:
> I don't understand how = differs with that semantic from :=
> I would expect that = would make a copy (clone?) of the object.
Assignment does copy the value between two containers, but in this
case, the value just happe
# New Ticket Created by "Stephen Simmons"
# Please include the string: [perl #58918]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58918 >
In r31096, use allows a program to use module A and module B, and allows
module B t
On Tue, Sep 16, 2008 at 5:14 AM, James Keenan via RT
<[EMAIL PROTECTED]> wrote:
> On Tue Sep 16 00:08:29 2008, [EMAIL PROTECTED] wrote:
>> On Monday 15 September 2008 20:06:11 James Keenan via RT wrote:
>>
>> > See patch attached. The patch eliminates smartlink-related code from
>> > Parrot, but d
57 matches
Mail list logo
