Will Coleda via RT wrote:
> On Sun Jun 01 11:06:10 2008, [EMAIL PROTECTED] wrote:
>> Hi,
>>
>> parrot + perl6 as of r28017 segfault for me while running
>> t/spec/S29-array/push.rakudo.
>> Attached is a reduced test case that produces an assertion failure with
>> --runcore=gcdebug:
>>
>> $ ../../
On Wed, Mar 5, 2008 at 9:31 PM, James E Keenan <[EMAIL PROTECTED]> wrote:
> From #parrotsketch yesterday, I learned of the existence of
> http://www.parrotblog.org/. I also learned (or, perhaps, re-learned) of the
> existence of http://planet.parrotcode.org/.
>
> What are the purpose and intended
On Mon Jun 02 13:19:16 2008, bernhard wrote:
>
> >
> > The previous version of the patch didn't work on Windows, because
pipe
> > open doesn't work there, grrr. Please try the attached version of
the
> > patch.
> >
>
> It looks like the current version of the patch has been applied.
> In r28
On Sun Jun 01 01:33:10 2008, [EMAIL PROTECTED] wrote:
> On Thursday 29 May 2008 06:21:03 Will Coleda wrote:
>
> > While this may have served a pedagogical purpose some time ago*,
> it's
> > better left in the docs as an example of what not to do (and that
> even
> > if core parrot is safe, we need
On Mon, Jun 2, 2008 at 11:38 PM, chromatic <[EMAIL PROTECTED]> wrote:
> On Monday 02 June 2008 20:25:28 Will Coleda via RT wrote:
>
>> And these are at least in part covered by other tickets (esp. the ones
>> referring to -0). We should separate out the remaining ones listed here
>> (assuming you a
On Fri, May 30, 2008 at 6:46 PM, Geoffrey Broadwell <[EMAIL PROTECTED]> wrote:
> On Fri, 2008-05-30 at 15:01 -0700, Geoffrey Broadwell wrote:
>> The most recent version of the patch got sent to the wrong mail alias;
>> I've reattached it below.
>
> ... And now regenerated, because I've broken out a
On Monday 02 June 2008 20:25:28 Will Coleda via RT wrote:
> And these are at least in part covered by other tickets (esp. the ones
> referring to -0). We should separate out the remaining ones listed here
> (assuming you agree with the list). (and I just fixed the trailing space
> error, so discou
On Sat Apr 26 13:54:01 2008, ajr wrote:
>
> On Windows XP Home Edition, using gcc, the following test error is
> occurring:
>
> Divide by zero^M
> current instr.: 'life' pc 175 (examples\pir\life.pir:102)
>
I am unable to duplicate this error. Can you provide more information about
your config
On Monday 02 June 2008 20:05:22 Bob Rogers wrote:
> Agreed, but doesn't this info really belong in README? Then DEVELOPING
> really only needs the middle paragraph, which is unchanging, and there
> would be one less file to have to update when cutting a new release.
>
>Or is there some purpos
On Sun Jun 01 11:06:10 2008, [EMAIL PROTECTED] wrote:
> Hi,
>
> parrot + perl6 as of r28017 segfault for me while running
> t/spec/S29-array/push.rakudo.
> Attached is a reduced test case that produces an assertion failure with
> --runcore=gcdebug:
>
> $ ../../parrot --runcore=gcdebug perl6.pbc p
Jerry, I am unable to duplicate all the errors with a more recent checkout on
my windows
box. I think I might be defaulting to the compiler that came with strawberry
perl, however,
so I'm not willing to simply close out the ticket.
Are you still seeing these errors with r28040? I'm getting th
From: "Will Coleda via RT" <[EMAIL PROTECTED]>
Date: Mon, 02 Jun 2008 19:31:15 -0700
On Tue May 20 20:53:06 2008, japhb wrote:
> What a developer might want to know is exactly the info described in the
> notes at the bottom of the file -- what was the last release, how long
> ha
On Tue May 27 10:57:50 2008, coke wrote:
> make[1]: Entering directory `/home/coke/sandbox/parrot-
> pdd25cx/compilers/tge'
> ../../parrot ../../runtime/parrot/library/PGE/Perl6Grammar.pbc
> --output=TGE/Parser.pir TGE/Parser.pg
> ../../parrot -o TGE/Parser.pbc --output-pbc TGE/Parser.pir
> Error r
On Tue May 20 20:53:06 2008, japhb wrote:
> Here's the current DEVELOPING file:
>
>
> # $Id$
>
> THIS RELEASE: Parrot 0.6.2 2008.05.20
> PREVIOUS RELEASE: Parrot 0.6.1 2008.04.15
>
> This file should only exist in development distributions. Delete it
> (and its entry in
On Mon, Jun 02, 2008 at 12:31:34PM +1000, Paul Fenwick wrote:
> G'day p6l and p5p,
>
> I'm currently working on the 'autodie' pragma for Perl 5, which is
> essentially 'Fatal' but with lexical scope. It's similar to the 'fatal'
> pragma described in S04/Exceptions.
>
> autodie is implementing an
No complaints, so I'm resolving the ticket. As a reminder, once you
have run Configure.pl, you can now call:
make codetest
or
perl t/harness --code-tests
Mark J. Reed wrote:
> The point is that %h[0] should be legal syntax that works on any hash,
> returning the "first" element. It doesn't matter if the elements are
> sorted or even sortable. You get an element. More to the point, if
> you don't add any elements to (or remove any elements from) th
The point is that %h[0] should be legal syntax that works on any hash,
returning the "first" element. It doesn't matter if the elements are
sorted or even sortable. You get an element. More to the point, if
you don't add any elements to (or remove any elements from) the hash,
you get the *same* e
David Green wrote:
> Jon Lang wrote:
>> If a routine is rw, you may optionally define a single "slurpy scalar"
>> (e.g., '*$value') in its signature. This scalar counts as the last
>> positional parameter, much like slurpy arrays and hashes must be declared
>> after all of the positional parameter
On Sunday 01 June 2008 19:31:34 Paul Fenwick wrote:
> Questions I'm seeking answers to are:
>
> * Is there a document that describes the current p6l exception hierarchy?
> My searching skills seem to be impaired today.
>
> * Does anyone have any input they'd like to make before I start fleshing
>
David Green wrote:
> Jon Lang wrote:
>> Bear in mind that keys are not necessarily sortable, let alone autosorted.
>> For instance, consider a hash that stores values keyed by complex numbers:
>> since there's no way to determine .before or .after when comparing two
>> complex numbers, there's no
On Monday 02 June 2008 12:27:17 Bernhard Schmalhofer wrote:
> The behavior of
>
> .sub main
>
> $N0 = 3.14159
> say $N0
> print $N0
> print "\n"
> .end
>
> surprised me, as I got:
>
>
> [EMAIL PROTECTED]:~/devel/Parrot/trunk$ uname -a
> Linux heist 2.6.24-17-generic #1 SMP Thu May 1 14:31:
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #55196]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=55196 >
The behavior of
.sub main
$N0 = 3.14159
say $N0
print $N0
print "\n"
.
# New Ticket Created by "Carl Mäsak"
# Please include the string: [perl #55184]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=55184 >
jonathan: how come `./perl6 -e '$_'` gives the error "too few
arguments passed (0) - 1
# New Ticket Created by Andrew Whitworth
# Please include the string: [perl #55170]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=55170 >
I'm not sure if this issue has been brought up before, and I'm also
not sure if it's
Ryan Richter wrote:
> Jon Lang wrote:
>> TSa wrote:
>> > John M. Dlugosz wrote:
>> >> The sqrt(2) should be a Num of 1.414213562373 with the precision of the
>> >> native floating-point that runs at full speed on the platform.
>> >
>> > That makes the Num type an Int with non-uniform spacing. E.g.
On 2008-Jun-1, at 1:50 pm, Jon Lang wrote:
David Green wrote:
[...] assignment should work like passing args when used on a
function. Then you can easily do whatever you want with it.
[...]
If a routine is rw, you may optionally define a single "slurpy
scalar" (e.g., '*$value') in its signa
On 2008-Jun-1, at 11:20 am, Jon Lang wrote:
David Green wrote:
I thought it already did, but apparently it's something that we
discussed
that didn't actually make it into S09. I agree that .[] should
apply to
hashes just as .{} can apply to arrays. The hashes don't even need
to be
sorted
On Mon, Jun 02, 2008 at 11:50:20AM -0700, Jon Lang wrote:
> TSa wrote:
> > John M. Dlugosz wrote:
> >> The sqrt(2) should be a Num of 1.414213562373 with the precision of the
> >> native floating-point that runs at full speed on the platform.
> >
> > That makes the Num type an Int with non-uniform
On Fri, May 9, 2008 at 9:10 AM, TSa <[EMAIL PROTECTED]> wrote:
> E.g. sqrt(2) might return a special Inf that can be lazily
> stringified to an arbitrary long sequence of digits of sqrt(2).
In what the heck mathematical world is the square root of two an
infinite value? Irrationality and infinitu
TSa wrote:
> John M. Dlugosz wrote:
>> The sqrt(2) should be a Num of 1.414213562373 with the precision of the
>> native floating-point that runs at full speed on the platform.
>
> That makes the Num type an Int with non-uniform spacing. E.g. there
> are Nums where $x++ == $x. And the -Inf and +Inf
Hi:
Both patches tested in 10.3/ppc and 10.4/intel and works OK for me
Paco
On Sun, Jun 1, 2008 at 4:29 PM, Seneca Cunningham via RT <
[EMAIL PROTECTED]> wrote:
> On Thu May 29 04:18:35 2008, [EMAIL PROTECTED] wrote:
> > We have another patch pending to config/init/hints/darwin.pm from
> > tetr
On Monday 02 June 2008 07:58:57 NotFound wrote:
> Previous version generates a warning when building with C, fixed now.
I like the general idea, but I wonder if there's something cleaner than an
environment variable. Nothing really comes to mind at the moment besides
making argument processing
HaloO,
John M. Dlugosz wrote:
The sqrt(2) should be a Num of 1.414213562373 with the precision of the
native floating-point that runs at full speed on the platform.
That makes the Num type an Int with non-uniform spacing. E.g. there
are Nums where $x++ == $x. And the -Inf and +Inf were better
Previous version generates a warning when building with C, fixed now.
--
Salu2
Index: src/runops_cores.c
===
--- src/runops_cores.c (revisión: 28033)
+++ src/runops_cores.c (copia de trabajo)
@@ -242,13 +242,28 @@
opcode_t *
runo
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Jun 2 13:00:04 2008 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with mo
36 matches
Mail list logo
