Re: Parrot build error/bug

2009-04-27 Thread chromatic
On Monday 27 April 2009 23:14:52 Michael wrote: > I'm running Fedora 11 (beta) on a Intel quad core CPU. > Below is the output of the "perl Configure.pl --gen-parrot" command: > Configuring Parrot ... > /usr/bin/perl Configure.pl > Can't locate Test

Re: Perl6 won't compile on Cygwin/Win (configure.pl won't run)

2009-05-18 Thread chromatic
On Monday 18 May 2009 12:20:47 Patrick R. Michaud wrote: > I'm more likely to suspect that something in your Parrot build is > causing parrot_config to not provide the SVN revision number for Parrot. I have an SVK checkout of Parrot, so Parrot's configuration process cannot determine the Parrot

Re: Perl6 won't compile on Cygwin/Win (configure.pl won't run)

2009-05-20 Thread chromatic
On Tuesday 19 May 2009 08:29:39 Patrick R. Michaud wrote: > On Mon, May 18, 2009 at 02:54:55PM -0700, chromatic wrote: > > I have an SVK checkout of Parrot, so Parrot's configuration process > > cannot determine the Parrot SVN revision. The problem here may be > >

Re: [perl #67278] non-awesome error message on 'class NewClass does OldClass'

2009-07-07 Thread chromatic
On Monday 06 July 2009 23:55:28 Moritz Lenz wrote: > I think abusing a class as a role is forbidden I hope it's not! -- c

Re: [perl #67358] [BUG] less than awesome error message for 1 param expected in Rakudo

2009-07-08 Thread chromatic
On Wednesday 08 July 2009 14:56:11 Kyle Hasselbacher wrote: > In this case, it might be easiest to leave the word out: > > Too many arguments passed (2) - 1 expected. > > Even this looks not too bad to me: > > Too many arguments passed (1) - 0 expected. It's Parrot behavior. It's trivial to chan

Re: [perl #67358] [BUG] less than awesome error message for 1 param expected in Rakudo

2009-07-10 Thread chromatic
On Wednesday 08 July 2009 17:24:47 yary wrote: > On Wed, Jul 8, 2009 at 3:28 PM, Carl Mäsak wrote: > > Maybe, but the problem as described in the original ticket was the > > inconsistency of '1' and 'params' with an 's'. > There's also the inconsistency of "arguments" vs "params"! Drop the > "pa

Rakudo Status and Parrot 2.0 (to be)

2010-01-15 Thread chromatic
Hello everyone, Parrot 2.0 will come out in less than a week, and I'd like to make sure that Rakudo #25 will work well with it. What's the current status, and are there any bugs or errors that need addressing before the release? -- c

Re: End-of-program global destruction is now guaranteed

2005-07-26 Thread chromatic
On Wed, 2005-07-27 at 02:18 +0800, Autrijus Tang wrote: > Heya. This is just a heads-up in response to your r5759: > > -- > r23564 (orig r5759): chromatic | 2005-07-23 03:30:54 +0800 > > Added tests for

Re: Documentation

2005-08-19 Thread chromatic
On Fri, 2005-08-19 at 09:15 -0600, Kevin Tew wrote: > Anyway, this is my first attempt at a pugs doc patch :) > Comments welcome! Welcome. I'm sure someone will offer you a commit bit very soon. In the meantime, my only comment is that, outside of class, module, file, and package names, where s

Re: Perl 6 Summary for 2005-11-14 through 2005-11-21

2005-11-22 Thread chromatic
On Wed, 2005-11-23 at 01:39 +0100, Leopold Toetsch wrote: > But my argument was: whenever you > start introspecting a call frame, by almost whatever means, this will > keep the call frame alive[1] (see Continuation or Closure). That is: > timely destruction doesn't work for example... Destruct

Re: make error on 9188

2006-02-27 Thread chromatic
On Monday 27 February 2006 16:35, Beau E. Cox wrote: > Is it me or thee? Any ideas out there? I'm seeing the same thing on Linux PPC. -- c

Re: make error on 9188

2006-03-03 Thread chromatic
On Wednesday 01 March 2006 11:19, Beau E. Cox wrote: > c - Did you have a chance to try my patch? If so, > did it work? It bypassed the build error, so that much definitely works better. I haven't finished running the test suite to see if everything else works. -- c

Re: The "lrep" thing

2006-03-10 Thread chromatic
On Thursday 09 March 2006 20:06, Flavio S. Glock wrote: > I'll not to be technical - I'm posting links to the programs, and the > #perl6 conversations are all logged in http://colabti.de - so feel > free to go read the sources. That's a big wad of code. Suppose I want to run it so I can see what

Re: State of Perl 6 Backends

2006-06-23 Thread chromatic
On Friday 23 June 2006 00:04, Swaroop C H wrote: > So, as of now, you envision svn:/pugs/misc/pX/Common/Pugs-Compiler-Perl6 to > be the "main" engine for Perl 6 ? I believe Audrey's point was that it is the most complete implementation right now. > If this is the case, is the purpose of the oth

Re: State of Perl 6 Backends

2006-06-23 Thread chromatic
On Friday 23 June 2006 12:19, Audrey Tang wrote: > Multiple implementations that are compatible to the spec, like the   > R5RS Scheme, are really a very good thing. Only insofar as the spec is complete enough that an implementation that adds nothing beyond that is useful and that there exists so

Re: Pm's YAPC::NA talk online

2006-06-28 Thread chromatic
On Wednesday 28 June 2006 02:26, João Cruz Morais wrote: > With that said I have some questions (i'm sorry if they were answered > already somewhere): > - Whats the point of using PGE+TGE over the good old LEX+YACC besides the > better regexps? Transforming trees with real objects is a lot easier

Re: designing a test suite for multiple implementations (tools thread)

2006-08-14 Thread chromatic
On Monday 14 August 2006 17:20, jerry gay wrote: > > I've added the plan for the neutral todo mechanism to Pugs' TASKS > > file, getting help from many others on #perl6. The new todo marks look > > like this: > > > >todo :pugs<6.28.0>, :p6p5<0.110>, :parrot<1.00>; > >is $got, $expected; #

Re: designing a test suite for multiple implementations (tools thread)

2006-08-14 Thread chromatic
On Monday 14 August 2006 18:53, jerry gay wrote: > moving todo() info out of these test files leads to fragile > test harnesses, as adding a test to the middle of a file will change test > numbers. if test descriptions are used, then unique descriptions for each > test are required. et cetera. Su

Re: Parrot, Perl 5 and performance

2007-03-12 Thread chromatic
On Monday 12 March 2007 14:29, [EMAIL PROTECTED] wrote: I wish I had better news for you, but I'm not sure anyone can answer your questions easily without a lot more information. > I'd like to get opinions from developers on this list. I'm looking > into this system that executes massive amounts

Re: question about t/operators/ternary.t

2007-06-20 Thread chromatic
On Wednesday 20 June 2007 15:53:59 Moritz Lenz wrote: > Basically I think that > - we need the test somewhere and > - it is not a test that one would usually write unless he/she found a > regression in one implementation. > > Therefore it would be good to have them somewhere separately, in an > im

Re: Bite-sized Tasks for the Interested (was Re: Standards bearers)

2007-12-13 Thread chromatic
On Thursday 13 December 2007 13:37:19 ispyhumanfly wrote: > Any questions? :) Is it possible to see a list of tasks without the barrier of creating an account, requesting an invite, or logging in? I understand that a little bit of administrative overhead is useful, but I'd also like to see as

Re: [perl #49168] [TODO] create a simplified command interface for perl6

2007-12-29 Thread chromatic
On Saturday 29 December 2007 01:29:46 Allison Randal wrote: > > * convert perl6.pbc into a C executable > Possible, but ultimately too constraining. There are significant > advantages to having the full Parrot runtime environment available. Don't reject this out of hand. The C executables gener

Re: Official Perl 6 and Parrot wikis

2007-12-29 Thread chromatic
On Saturday 29 December 2007 06:56:45 Mark J. Reed wrote: > Maybe it's just me, but it > seems like it will just feed the all-too-common perception that Perl > is for CGI scripts, and "real" web apps need to be written in > something else (be it Java, PHP, Ruby/Rails, whatever). Proposed new rule

Re: Official Perl 6 and Parrot wikis

2007-12-29 Thread chromatic
On Saturday 29 December 2007 13:35:00 Mark J. Reed wrote: > Ok, consider me duly chastised. Sorry for the sidetracking. It's not a *bad* idea, but it's less important in my mind than getting useful information on the wiki. Anyone who wants to pursue it can do so, but I'd like to forestall a l

Re: Perl 6 fundraising and related topics.

2008-02-21 Thread chromatic
On Thursday 21 February 2008 06:25:42 Joshua Gatcomb wrote: > Here is something to consider.  Unless we can afford to fund an individual > full time with enough money for them to pay for their own health coverage > and other benefits, the amount of time they are volunteering is already as > much a

Re: [perl #51116] [BUG] languages/perl6/perl6 --target=past ignores -e

2008-02-23 Thread chromatic
On Friday 22 February 2008 16:50:35 Mitchell N Charity wrote: > languages/perl6/perl6 --target=past gives no output with -e CODE. > r25997 on fedora 8, x86_64. > > # works > $ languages/perl6/perl6 -e 'say(3);' > 3 > > # works > $ echo -n 'say(3);' > deleteme.pm; languages/perl6/perl6 --target=pas

Re: [perl #53040] rakdudo : code generated by --target=pir does not execute in parrot

2008-04-18 Thread chromatic
On Friday 18 April 2008 07:45:43 Patrick R. Michaud wrote: > On Fri, Apr 18, 2008 at 06:30:24AM -0700, Stephane Payrard wrote: > > The error message is "No such caller depth" > > Having it working would be a additional tool. > > Indeed, I wanted to tweak the code manually to see the code I needed

Re: Clarification of t/spec/S29-array/delete.t

2008-05-29 Thread chromatic
On Wednesday 28 May 2008 23:20:15 Patrick R. Michaud wrote: > In particular, I think that the following sequence should > result in a 0-length array: > > my @array; > @array[8] = 'eight';# array has elements 0..8 > @array.delete(8); # now it's empty again >

Re: [perl #55782] [BUG] for 1..1000 -> $a { say $a } segfaults in rakudo (Gargbage Collector)

2008-06-15 Thread chromatic
On Saturday 14 June 2008 09:54:09 Moritz Lenz wrote: > As AnonMonk reported here: http://www.perlmonks.org/?node_id=692090 the > line for 1..1000 -> $a { say $a } > segfaults in rakudo. > > The problem can be reproduced by creating a Range with --runcore=gcdebug: > > ../../parrot --runcore=gcdebug

Re: [perl #56454] [BUG] Another -G bug. With PIR

2008-06-29 Thread chromatic
On Sunday 29 June 2008 18:17:16 luben karavelov wrote: > The source of the program (dumb fibonacci numbers) is as follows: > > use v6; > > sub fib( $n ){ > if ( $n < 2 ) { > $n; > } else { > fib($n-1)+fib($n-2); > } > } > > say fib(11); > > it dies with segmentation fau

Re: [perl #56618] [BUG] rakudo segfaults calling subs in a namespace

2008-07-05 Thread chromatic
On Saturday 05 July 2008 09:42:33 Jeff Horwitz wrote: > In r29081, the following code segfaults: > >module Foo::Bar; >sub foo() { say "bar"; } >foo(); # segfaults here > > The script works if the modules declaration is omitted. I also tried > running with -G, and it still segfaults at

Re: [perl #57626] [BUG] perl6 -e 'say "hello"' ==> Segmentation fault

2008-08-05 Thread chromatic
On Tuesday 05 August 2008 07:50:41 [EMAIL PROTECTED] (via RT) wrote: > * Today I downloaded parrot-0.6.4 to my Debian PC. > * I also installed the libicu-dev, libicu38 packages before configuration > * cd parrot-0.6.4; perl Configure.pl; make; cd languages/perl6; make perl6 > * It seems that every

Re: [perl #57710] Parrot segfaults after subtype type check fails

2008-08-07 Thread chromatic
On Thursday 07 August 2008 05:16:40 Carl Mäsak wrote: > r30087: > $ ./perl6 -e 'subset A of Int where 1; my A $a = 1' # this works > $ ./perl6 -e 'subset A of Int where 1; my A $a = 0' # this fails (as > it should) but segfaults > Type check failed > [...] > Segmentation fault > > I was not able t

Re: [perl #57740] Dotty method calls confuse rakudo's MMD mechanism

2008-08-09 Thread chromatic
On Thursday 07 August 2008 22:45:36 Carl Mäsak wrote: > The segfault only occurs when running ./perl6, not when running > ../../parrot perl6.pbc. That's because all fakecutables set the flag which tells Parrot to destroy everything at shutdown. If you add the --leak-test or --destroy-at-end fla

Re: [perl #57882] Trying to assign to a class attribute within a class declaration in rakudo makes Parrot segfault

2008-08-13 Thread chromatic
On Tuesday 12 August 2008 14:17:22 Carl Mäsak wrote: > # New Ticket Created by "Carl Mäsak" > # Please include the string: [perl #57882] > # in the subject line of all future correspondence about this issue. > # http://rt.perl.org/rt3/Ticket/Display.html?id=57882 > > > > r30188: > $ ./perl6 -e 'c

Re: [perl #58392] Recursion and for loops interact badly in Rakudo

2008-09-03 Thread chromatic
On Wednesday 27 August 2008 07:26:00 Moritz Lenz wrote: > Carl MXXsak (via RT) wrote: > > r30589: > > $ cat for-loop-recursion.bug > > sub f($l) { > > return() if $l <= 0; > > say "entering $l"; > > for 1..3 { > > f($l-1); > > say "looping in $l"; > > } > > } > > f(2);

Re: [perl #58578] [BUG] Segementation fault after a ~500 regex compilations + matches

2008-09-04 Thread chromatic
On Thursday 04 September 2008 11:40:36 Moritz Lenz wrote: > # New Ticket Created by Moritz Lenz > # Please include the string: [perl #58578] > # in the subject line of all future correspondence about this issue. > # http://rt.perl.org/rt3/Ticket/Display.html?id=58578 > > > > Rakudo r30754 segfau

Re: [perl #58578] [BUG] Segementation fault after a ~500 regex compilations + matches

2008-09-04 Thread chromatic
On Thursday 04 September 2008 17:43:55 chromatic wrote: > Run it through GDB, and it looks like Parrot runs out of stack space > recursively throwing exceptions. If someone modifies Rakudo not to catch > the topmost exception, I bet we could track this down faster. ... and here'

Re: [perl #57338] parrot segfaults after nonexistent method is called from within sub invoked without parens in rakudo

2008-09-11 Thread chromatic
On Thursday 11 September 2008 07:17:56 Carl Mäsak wrote: > Jonathan (>), Carl (>>): > >> This also works, but segfaults: > >> > >> $ ./perl6 -e 'class A {}; sub c { say A.new.b() }; c' > >> Method 'b' not found for invocant of class 'A' > >> current instr.: 'c' pc 99 (EVAL_13:42) > >> called from

Re: method signature issues

2008-09-20 Thread chromatic
On Friday 19 September 2008 21:46:53 Chris Davaz wrote: > In any-str.pir we need to figure out how to change > > .sub 'split' :method :multi('String') > > into > > .sub 'split' :method :multi(_, 'String') > > since the former method signature is causing problems for me as I'm > trying to implement

Re: method signature issues

2008-09-20 Thread chromatic
On Saturday 20 September 2008 22:24:52 Chris Davaz wrote: > If it is the case that :method and :multi are incompatible, I am a bit > surprised to see that in the Rakudo src directory: I said they're incompatible -- meant in terms of their semantics. I didn't say they don't work together in some

Re: method signature issues

2008-09-21 Thread chromatic
On Sunday 21 September 2008 03:53:31 Jonathan Worthington wrote: > > I said they're incompatible -- meant in terms of their semantics.  I > > didn't say they don't work together in some cases with our current > > implementation. (They probably shouldn't.) > They probably should. If they didn't, t

Re: [perl #59244] [TODO] Implement infix: for Pairs

2008-09-24 Thread chromatic
On Tuesday 23 September 2008 09:35:05 Moritz Lenz wrote: > %hash.pairs.sort needs infix: to work properly with Pair as input. > > It should be easy to add a multi that does this by first comparing the > key, and if they are equal the value. > > When this is done most (or all) of the skip markers i

Re: [perl #59308] Test failures due to integer overflow

2008-09-25 Thread chromatic
ler;compile' pc 438 > (src/PCT/HLLCompiler.pir:303) > [...] > > I suspect it might be this commit: > > r31402 | chromatic | 2008-09-25 07:30:31 +0200 (Thu, 25 Sep 2008) | 7 lines > > [src] Expanded float precision to 15 digits from 6. One side effect is > that floa

Re: [RFC][PATCH] Rename Rakudo's "spectest_regression" to "spectest"

2008-10-10 Thread chromatic
On Friday 10 October 2008 06:45:16 jerry gay wrote: > during this week's design meeting, i mentioned that i think it's time > to rename 'spectest_regression' to 'test'. we didn't discuss it much, > but i imagine something like: > >   test : coretest codetest spectest_regression > > with appropriat

Re: [perl #57402] [BUG] GC-related segfault in t/spec/S12-class/attributes.t

2008-10-18 Thread chromatic
On Wednesday 30 July 2008 01:45:10 Moritz Lenz wrote: > r29870 on i386 Debian GNU/Linux 32 bit, after a fresh checkout: > > ../../parrot perl6.pbc t/spec/S12-class/attributes.t > Segmentation fault > > Calling the same either with the -G option to parrot or with perl6.pir > instead of perl6.pbc wo

Re: [perl #60176] Rakudo fails on defining classes with core roles

2008-11-04 Thread chromatic
On Tuesday 04 November 2008 09:05:13 [EMAIL PROTECTED] via RT wrote: > On Mon Oct 27 10:55:52 2008, masak wrote: > > Rakudo r32151 can't create classes with roles from the Rakudo-defined > > classes. > > > > $ ./perl6 -e 'role B {}; class A does B {}' # this works > > > > $ perl6 -e 'class A does

Re: [perl #58602] subset types and multi dispatch don't mix

2008-11-11 Thread chromatic
On Sunday 14 September 2008 12:48:07 Moritz Lenz wrote: > Currently (r31122) the example dies with "Ambiguous dispatch.". > > (On a related note, could we get more verbose error messages? "Ambiguous > dispatch for { sub | method } $name" would be more helpful.) Added in r32552. -- c

Parrot 0.8.1 "Tio Richie" Released!

2008-11-18 Thread chromatic
On behalf of the Parrot team, I'm proud to announce Parrot 0.8.1 "Tio Richie." [1] Parrot is a virtual machine aimed at running all dynamic languages. Rat Creature #1: Comrade! We are about to feast! Quick, get your fat carcass behind this bush and get ready! Rat Creature

Re: [perl #60910] rakudo failing reverse.t and abs.t

2008-11-30 Thread chromatic
On Friday 28 November 2008 16:10:14 Patrick R. Michaud (via RT) wrote: > Something changed between r33248 and 33263 that causes > Rakudo to fail the S29-list/reverse.t and S29-num/abs.t > spectests. The revisions in question had to do with > changing namespaces and multisub PMCs, but I don't know

Re: [perl #62730] Internal Parrot errors leak through when passing some kinds of pairs

2009-01-29 Thread chromatic
On Wednesday 28 January 2009 05:43:08 jn...@jnthn.net via RT wrote: > I figured this would be easy to fix, but it's not. Basically, because > for infix:=> we could have any complex expression that generates a key > on the RHS, and Parrot does not allow us to pass named arguments where > the name i

Re: [perl #62730] Internal Parrot errors leak through when passing some kinds of pairs

2009-01-29 Thread chromatic
On Thursday 29 January 2009 02:14:23 Jonathan Worthington wrote: > > Can you show some example PIR code that should work? > > Ah, yes, sorry... > > .sub 'main' > $S0 = 'foo' > example('foo'=>42) # works > # example($S0=>42) # what I want to work also > .end > > .sub 'example' > .pa