On Tue, Jul 1, 2008 at 7:17 AM, Will Coleda via RT
<[EMAIL PROTECTED]> wrote:
> On Thu Jun 26 11:01:00 2008, [EMAIL PROTECTED] wrote:
>> chromatic wrote:
>>
>> > T::H 3 is only a requirement for people who want to type 'make
>> smolder' (and
>> > eventually I hope 'make smoke'), so probing for it w
On Sun, Sep 7, 2008 at 2:07 PM, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> On Sat, 6 Sep 2008, Christoph Otto via RT wrote:
>
>> On Wed May 10 11:01:34 2006, stmpeters wrote:
>> >
>> > I'm taking a look at it. I should have something working this evening
>> > for the configs. Adding the HAS_BLAH
On Tue Jun 03 13:05:37 2008, [EMAIL PROTECTED] wrote:
>
> I wonder if setting the SVKROOT environment variable to something
unlikely
> would help simulate this.
>
> $ENV{SVKROOT} = 'you must be kidding me';
>
I tried this tonight in two locations: my iBook, where I once tried to
install
Moritz Lenz moritz-at-casella.verplant.org |Perl 6| wrote:
map *is* lazy, as are all list builtins that can be lazy (which doesn't
include stuff like sort, which has to look at all items anyway).
Are you sure that it doesn't imply order of evaluation by default? I'm
all for it (to be diff
I updated the wiki a little about this.
http://www.perlfoundation.org/parrot/index.cgi?rfp_parrot_needs_better_smoke_reports
On Sun, Aug 17, 2008 at 9:20 AM, mhelix <[EMAIL PROTECTED]> wrote:
> The first named parameter isn't set if optional parameters are missing. The
> function Parrot_process_args didn't
> save the value of the argument. I used memcpy to copy the UnionVal. If
> there's a neater way to do that please
Since there have been no complaints or further discussion about this
issue in nearly 3 months, I am resolving the ticket.
kid51
This ticket has not been addressed since early July. Re-reading it now,
it seems to have two major discussion threads: one specific to
Test::Harness 3 and one relating more generally to the versions of CPAN
modules needed to configure, build and test Parrot.
May I ask for those who have posted t
On Sat Aug 16 07:36:44 2008, [EMAIL PROTECTED] wrote:
> - Update grammar.pg (short-term), or wait for STD.pm integration
Done in r30864.
On Thu Jun 12 10:23:06 2008, [EMAIL PROTECTED] wrote:
> On Thursday 12 June 2008 10:01:21 NotFound wrote:
>
> > Some more details: adding:
> >
> > Parrot_set_flag(interp, PARROT_DESTROY_FLAG);
> >
> > in src/main.c it segfaults also when executing with perl6.pbc, and
> > also a lot of parrot test
No one objected to resolving this ticket, so I am doing so now. New
Smolder issues? Open a new RT.
John M. Dlugosz wrote:
> Consider something like a 'map' call, only I want it to be lazy.
map *is* lazy, as are all list builtins that can be lazy (which doesn't
include stuff like sort, which has to look at all items anyway).
> I know that a
> list can contain internally iterators that generat
Consider something like a 'map' call, only I want it to be lazy. I know that a
list can contain internally iterators that generate elements as needed or
perhaps in the background. But how do you create such a thing? Something like:
@lazy_list := parallel-map { get_info($_) } @filenames;
On Sat, 6 Sep 2008, Christoph Otto via RT wrote:
> On Wed May 10 11:01:34 2006, stmpeters wrote:
> >
> > I'm taking a look at it. I should have something working this evening
> > for the configs. Adding the HAS_BLAH's will take some additional time.
> >
> > Steve Peters
> > [EMAIL PROTECTED]
On Sun, Sep 07, 2008 at 06:33:49AM -0700, Vasily Chekalkin wrote:
> Hello.
>
> By default Range (and probably many other classes) constructed in
> non-consistent state.
>
> Minimal example:
> .namespace
> .sub 'main'
> load_bytecode "perl6.pbc"
> $P0 = new 'Range'
> $P1 = clone $P0
>
No objections and no problems, closing ticket.
# New Ticket Created by Vasily Chekalkin
# Please include the string: [perl #58642]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58642 >
Hello.
By default Range (and probably many other classes) constructed in
non-consi
TSa (Thomas Sandlaß) thomas-at-sandlass.de |Perl 6| wrote:
a() proceed: orelse b();
CATCH
{
... # make $! into return value
goto proceed;
}
This kind of needs to know the variable the return value of a()
is stored into. This is easy if orelse is checking $! anyway.
But do
Patrick R. Michaud (via RT) wrote:
> # New Ticket Created by Patrick R. Michaud
> # Please include the string: [perl #58644]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=58644 >
>
>
> The rindex method added in r30858
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #58646]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58646 >
For rakudo builtin functions that are written in PIR, use
.return '!FAIL'('..
coke says:
> The PIR code in this ticket now causes a Bus error on osx/386 (r25175)
Also segfaults in linux/386 for me.
I added an assertion that catch the fault in r30859
--
Salu2
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #58644]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58644 >
The rindex method added in r30858 has a bug:
$ ./parrot perl6.pbc
> say 85224.rin
"TSa (Thomas Sandlaß)" schreef:
> Larry Wall:
>> Another potential issue is that CATCH doesn't distinguish exceptions
>> coming from the current block from those coming from the subcall to
>> a(). So it could end up returning Failure from the current block when
>> you intended to force return of F
HaloO,
On Thursday, 4. September 2008 03:39:20 Larry Wall wrote:
> Another potential issue is that CATCH doesn't distinguish exceptions
> coming from the current block from those coming from the subcall to a().
> So it could end up returning Failure from the current block when
> you intended to fo
On Wed May 10 11:01:34 2006, stmpeters wrote:
>
> I'm taking a look at it. I should have something working this evening
> for the configs. Adding the HAS_BLAH's will take some additional time.
>
> Steve Peters
> [EMAIL PROTECTED]
"when useful" is vague does not indicate why the extra configu
On Tue Aug 05 04:09:14 2008, tene wrote:
> pdd23:
>
> Exception handlers can resume execution immediately after the
> "throw" opcode by invoking the resume continuation which is stored
> in the exception object. That continuation must be invoked with no
> parameters; in other words, "throw" never
There are some tests for List.uniq in the test suite, and pugs
implements it, but it's not in S29.
Damian seems to have though we should have it:
http://groups.google.com/group/perl.perl6.language/msg/4c8c9bd73c862bed
So should we have it? If not, I'll replace the tests with
eval_dies_ok('(1, 2).
On Tue Aug 26 18:39:55 2008, rgrjr wrote:
>From: Klaas-Jan Stol (via RT) <[EMAIL PROTECTED]>
>Date: Tue, 26 Aug 2008 04:46:56 -0700
>
>From PDD19:
>
>Identifiers don't have any limit on length at the moment, but some
>sane-but-generous length limit may be imposed in the future
On Sat Jul 05 02:53:11 2008, bernhard wrote:
> In runtime/parrot/library/config.pir I encountered the comment.
>
>XXX hash should probably be marked read-only..
>
> This should be investigated.
>
> Regards,
> Bernhard
This seems to be a very sane suggestion. It's implemented and has a
t
On Sat May 17 14:55:53 2008, pmichaud wrote:
> On Mon Jun 12 16:30:13 2006, jonathan wrote:
> > Both Parrot_store_global and store_sub call
> Parrot_invalidate_method_cache,
> > however the versions of these that take keys (Parrot_store_global_p and
> > store_sub_p) fail to do so.
>
> Is this t
On Tue Feb 05 06:50:24 2008, coke wrote:
> On Wed Aug 16 23:09:16 2006, mdiep wrote:
> > I don't know how to write a test for this off the top of my head, but
> > Iterator and DynLexPad don't play well together atm. When I tried, I
> > got this error:
> >
> > elements() not implemented in
# New Ticket Created by chromatic
# Please include the string: [perl #58636]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=58636 >
Patrick's example code for RT #30843 creates an infinite loop (before the
workaround check
Author: cotto
Date: Sat Sep 6 15:52:59 2008
New Revision: 30838
Modified:
trunk/docs/pdds/pdd23_exceptions.pod
Log:
[pdd] make the exception-throwing example in pdd23 work
Modified: trunk/docs/pdds/pdd23_exceptions.pod
On Sat Sep 06 15:51:16 2008, julianalbo wrote:
> Sorry, the code I poste was bad. The valid form is:
>
> $P1 = new ['Exception'], $P0 # create new exception object
>
I've changed the example code to use the more common syntax without
brackets:
$P1 = new 'Exception', $P0
. The code works now, s
Last revision of string.pmc patch, and of t/pmc/string.t patch,
applied in r30853
See the ticket, several messages where not CCed to the list.
--
Salu2
35 matches
Mail list logo
