[perl #41168] graceful "no compiler" error message?

2007-03-18 Thread Paul Cochrane via RT
On Sat Mar 17 23:51:04 2007, [EMAIL PROTECTED] wrote: > On Wed Jan 03 07:51:56 2007, coke wrote: > > > It would be nice if configure.pl gracefully handled the error > condition > of "no compiler found". > > Here's a patch for that! Patch applied in r17614. Thanks!

[perl #39908] [BUG] IMCC treats $S as a non-register instead of throwing an error

2007-03-18 Thread Nuno Carvalho via RT
Greetings, On Thu Mar 15 06:32:28 2007, particle wrote: > On 3/14/07, Nuno Carvalho via RT <[EMAIL PROTECTED]> > wrote: > > Greetings, > > > > here are some examples running the changed lexer: > > > > $ cat 1.pir > > .sub main :main > > .macro SpinForever (Count) > > .local $LOOP: dec

[perl #41883] [BUG] PMETHODs.pm doesn't change back the filename

2007-03-18 Thread via RT
# New Ticket Created by Joshua Isom # Please include the string: [perl #41883] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41883 > In lib/Parrot/Pmc2c/PMETHODs.pm, the file name reported by gcc is changed to be the PMET

[perl #41168] graceful "no compiler" error message?

2007-03-18 Thread Paul Cochrane via RT
On Sun Mar 18 04:05:41 2007, ptc wrote: > On Sat Mar 17 23:51:04 2007, [EMAIL PROTECTED] wrote: > > On Wed Jan 03 07:51:56 2007, coke wrote: > > > > > It would be nice if configure.pl gracefully handled the error > > condition > of "no compiler found". > > > > Here's a patch for that! > > Patch

[perl #38764] Test results of parrot on Freebsd

2007-03-18 Thread Paul Cochrane via RT
I've now got access to a FreeBSD (6.1 PRERELEASE #4) box, and have checked out and compiled Parrot. Attached is the output of 'make test', and myconfig. Regards, Paul myconfig Description: Binary data make_test.out Description: Binary data

[perl #41601] [BUG] parrotbug b0rken

2007-03-18 Thread Paul Cochrane via RT
On Fri Feb 23 13:32:02 2007, kjs wrote: > parrotbug seems to be broken on win32. What output are you getting (if at all)?

the value of maintaining a working install target to the parrot project

2007-03-18 Thread Mike Mattie
Hello, -> 1. Introduction I am a programmer interested in the parrot vm. In my spare time I have attempted several times to 'get into' parrot. This time I have progressed much further, and in doing so I have developed a perspective that is informed enough for me to hazard some input on the projec

Re: Failure Rant (was [BUG]: t/pmc/metaclass.t fails on Darwin)

2007-03-18 Thread chromatic
On Saturday 17 March 2007 18:12, Jonathan Worthington wrote: > Not to pass the buck or anything, but it wasn't me that wrote and > checked in the test in the first place, I'm just working on the issue > raised by the test. I'd prefer that you just ranted about issues rather > than at/about individ

[perl #41658] [TODO] Move all gc source files into a separate directory

2007-03-18 Thread Paul Cochrane via RT
On Thu Mar 15 19:47:07 2007, [EMAIL PROTECTED] wrote: > I have a patch for doing this, at least a build, compile, and test type > patch. Instead of doing one massive patch to send, here's a script to > move the files(diffs include the entire file twice) and apply the > patch. It moves all th

parrot-0.4.9 ebuild for the gentoo distribution (WIP)

2007-03-18 Thread Mike Mattie
Hello, I have been working on a gentoo ebuild for the parrot-0.4.9 release. I have commented more extensively on the install target in a mail: "the value of maintaining a working install target to the parrot project" This ebuild is provided for reference in discussion of the points raised in th

[perl #41889] [PATCH] hoist cut and paste duplication into a function in src/library.c, also possible win32 bug found ?

2007-03-18 Thread via RT
# New Ticket Created by Mike Mattie # Please include the string: [perl #41889] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41889 > Hello, While mucking around in src/library.c I noticed some cut & paste duplication. It

Re: [perl #41889] [PATCH] hoist cut and paste duplication into a function in src/library.c, also possible win32 bug found ?

2007-03-18 Thread Jonathan Worthington
Mike Mattie (via RT) wrote: While mucking around in src/library.c I noticed some cut & paste duplication. It looked like a fairly simple hoist so I have attached the changes I made. I do not have a win32 platform available for testing so I haven't been able to compile test it. while ( (cn

[perl #41505] [CAGE] Cleanup and reorganise documentation related to svn properties

2007-03-18 Thread Allison Randal via RT
Made a few more text edits in r17591. Paul Cochrane's changes approved, ticket resolved.

[perl #38988] [PDD] review pdd07_codingstd.pod

2007-03-18 Thread Will Coleda via RT
Noticed this still has the marker: =head2 CHIP HAS EDITED THIS FAR INTO THE FILE +---+ Everything below this point must still be reviewed +---+ in it, despite being moved out of the cl

[perl #41885] [BUG] All the dynoplibs/dynpmcs fail on freebsd

2007-03-18 Thread via RT
# New Ticket Created by Joshua Isom # Please include the string: [perl #41885] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41885 > Currently(and I don't know how long it's been going on, but it's relatively new), but al

[perl #41529] [BUG]: t/perl/Parrot_Distribution.t test failure

2007-03-18 Thread Paul Cochrane via RT
On Tue Feb 20 15:31:02 2007, [EMAIL PROTECTED] wrote: > On Saturday 17 February 2007 08:27, jerry gay wrote: > > > as noted in my svn log at time of checkin, this is a failing test > > which exposes a bug in Parrot::Distribution. '*.t' files are only perl > > files if the shebang says they are, b

[perl #41895] [TODO] Use Getopt for argument parsing in perlcritic.t

2007-03-18 Thread via RT
# New Ticket Created by Paul Cochrane # Please include the string: [perl #41895] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41895 > t/codingstd/perlcritic.t uses a non-standard argument parsing mechanism. This should b

[svn:parrot-pdd] r17581 - trunk/docs/pdds

2007-03-18 Thread paultcochrane
Author: paultcochrane Date: Sat Mar 17 15:54:50 2007 New Revision: 17581 Modified: trunk/docs/pdds/pdd07_codingstd.pod Log: [docs] Gleaned as much info as possible from docs/submissions.pod, http://www.parrotcode.org/source.html and t/distro/file_metadata.t on the topic of subversion propertie

[perl #41884] [PATCH] gcc/mingw32-make compilation failure under MSWin32

2007-03-18 Thread via RT
# New Ticket Created by Alexandr Ciornii # Please include the string: [perl #41884] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41884 > Compilation with gcc/mingw32-make failed due to incorect value of 'slash' found by

Re: request new Mapping|Hash operators

2007-03-18 Thread Aaron Crane
David Green writes: > In the meantime, Darren's proposal still raises a lot of interesting > language questions. For example, how *do* you rename a hash key? That's easy even in Perl 5. This modifies %hash in-place: my @values = delete @[EMAIL PROTECTED]; @[EMAIL PROTECTED] = @values; Whil

[perl #41878] [TODO] create exporter pmc

2007-03-18 Thread via RT
# New Ticket Created by Jerry Gay # Please include the string: [perl #41878] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41878 > allison replaced the .IMPORT macro, used for importing pmcs into the current namespace, wit

Re: [perl #41885] [BUG] All the dynoplibs/dynpmcs fail on freebsd

2007-03-18 Thread Paul Cochrane
Currently(and I don't know how long it's been going on, but it's relatively new), but all of the dynoplib tests and all of the dynpmc tests fail on FreeBSD 6.0. All tests fail as a syntax error. I can confirm this on FreeBSD 6.1 as well. Paul

Re: [perl #38764] Test results of parrot on Freebsd

2007-03-18 Thread chromatic
On Sunday 18 March 2007 07:41, Paul Cochrane via RT wrote: > I've now got access to a FreeBSD (6.1 PRERELEASE #4) box, and have > checked out and compiled Parrot. Attached is the output of 'make > test', and myconfig. I have the t/stm/llqueue.t failure on my box and dug into it last night. The

Re: [perl #41601] [BUG] parrotbug b0rken

2007-03-18 Thread Nicholas Clark
On Sun, Mar 18, 2007 at 10:38:14AM -0700, Paul Cochrane via RT wrote: > The main problem people seem to be having with parrotbug is in sending > messages. Since one needs to be online to send messages (if and when > it works) why not let people just use [EMAIL PROTECTED] Then > we can reserve

[perl #41896] [BUG] p5rx tests consuming infinite resources on win32

2007-03-18 Thread via RT
# New Ticket Created by Jerry Gay # Please include the string: [perl #41896] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=41896 > at r17619, i'm unable to run make test, due to failures in p5rx tests. actually, none of th

Re: [perl #41601] [BUG] parrotbug b0rken

2007-03-18 Thread Jerome Quelin
On 07/03/18 18:06 +, Nicholas Clark wrote: > On Sun, Mar 18, 2007 at 06:51:32PM +0100, Paul Cochrane wrote: > > parrotbug also has the save option, and it saves a lot of > > configuration information. I'm asking if the "send" feature can be > > removed, which is the bit which seems to be broke

Re: [perl #38764] Test results of parrot on Freebsd

2007-03-18 Thread Paul Cochrane
On 18/03/07, chromatic <[EMAIL PROTECTED]> wrote: On Sunday 18 March 2007 07:41, Paul Cochrane via RT wrote: > I've now got access to a FreeBSD (6.1 PRERELEASE #4) box, and have > checked out and compiled Parrot. Attached is the output of 'make > test', and myconfig. I have the t/stm/llqueue.t

Re: [perl #41886] [CAGE] Use lcov to show code coverage

2007-03-18 Thread Paul Johnson
On Sat, Mar 17, 2007 at 02:19:51PM -0700, Paul Cochrane wrote: > The lcov tool from the Linux Test Project > (http://ltp.sourceforge.net/coverage/lcov.readme.php) can be used to > produce html output of code coverage information (I believe this looks > similar to Devel::Cover's output). A 'make c

Re: [perl #41889] [PATCH] hoist cut and paste duplication into a function in src/library.c, also possible win32 bug found ?

2007-03-18 Thread Mike Mattie
On Sun, 18 Mar 2007 19:30:35 + Nicholas Clark <[EMAIL PROTECTED]> wrote: > On Sun, Mar 18, 2007 at 03:35:14PM +, Jonathan Worthington wrote: > > Mike Mattie (via RT) wrote: > > >While mucking around in src/library.c I noticed some cut & paste > > >duplication. It looked like a fairly simp

[svn:parrot-pdd] r17591 - trunk/docs/pdds

2007-03-18 Thread allison
Author: allison Date: Sat Mar 17 22:06:26 2007 New Revision: 17591 Modified: trunk/docs/pdds/pdd07_codingstd.pod Log: [pdd]: A few edits to coding standards after addition of svn properties text. Modified: trunk/docs/pdds/pdd07_codingstd.pod ==

Re: [perl #41889] [PATCH] hoist cut and paste duplication into a function in src/library.c, also possible win32 bug found ?

2007-03-18 Thread Joshua Juran
On Mar 18, 2007, at 3:59 PM, Mike Mattie wrote: On Sun, 18 Mar 2007 19:30:35 + Nicholas Clark <[EMAIL PROTECTED]> wrote: On Sun, Mar 18, 2007 at 03:35:14PM +, Jonathan Worthington wrote: Mike Mattie (via RT) wrote: While mucking around in src/library.c I noticed some cut & paste dupl

Re: [perl #41601] [BUG] parrotbug b0rken

2007-03-18 Thread Paul Cochrane
In Perl 5 land, the advantage of the perlbug program is that it captures the output of perl -V, which is often invaluable in categorising or identifying the cause of bugs. e-mail to [EMAIL PROTECTED] doesn't always have this. perlbug has the option to save the bug report to a file, which can then

Re: [perl #41889] [PATCH] hoist cut and paste duplication into a function in src/library.c, also possible win32 bug found ?

2007-03-18 Thread Jonathan Worthington
Mike Mattie (via RT) wrote: While mucking around in src/library.c I noticed some cut & paste duplication. It looked like a fairly simple hoist so I have attached the changes I made. Needed a small fix (note: C89, declarations must come first in a block). Did that, and it's now applied in r17

Re: [perl #41896] [BUG] p5rx tests consuming infinite resources on win32

2007-03-18 Thread chromatic
On Sunday 18 March 2007 10:06, Jerry Gay wrote: > at r17619, i'm unable to run make test, due to failures in p5rx tests. > actually, none of them are failing, but my system becomes > non-responsive. after approximately test 200, tests (and there are > over 900) take a few seconds each to complete,

Re: Synopsis 26

2007-03-18 Thread jerry gay
On 3/18/07, Thom Boyer <[EMAIL PROTECTED]> wrote: I never could find the Pod-to-XHTML'd version of S26 -- the document attached to that email was S26.pod6, not S26.xhtml. I don't want to bug Damian, because obviously he has enough of life "happening", as it were. But is the XHTML'd version of S2

Re: request new Mapping|Hash operators

2007-03-18 Thread Uri Guttman
> "AC" == Aaron Crane <[EMAIL PROTECTED]> writes: AC> That's easy even in Perl 5. This modifies %hash in-place: AC> my @values = AC> @[EMAIL PROTECTED] = @values; you can even do: @[EMAIL PROTECTED] = delete @[EMAIL PROTECTED]; and i am sure a simple p6 thing can be wri

Re: request new Mapping|Hash operators

2007-03-18 Thread Darren Duncan
On Sun, 18 Mar 2007, Uri Guttman wrote: > as for rename on hash keys, why not call it rekey? also even if it is > called rename as a hash method it is different than rename as a function > to rename a file so there is no ambiguity. The name "rekey" or some such sounds like a reasonable name, and i

Re: request new Mapping|Hash operators

2007-03-18 Thread Darren Duncan
On Sun, 18 Mar 2007, Aaron Crane wrote: > David Green writes: > > In the meantime, Darren's proposal still raises a lot of interesting > > language questions. For example, how *do* you rename a hash key? > > That's easy even in Perl 5. This modifies %hash in-place: > > my @values = delete @[E

[perl #41601] [BUG] parrotbug b0rken

2007-03-18 Thread Paul Cochrane via RT
The main problem people seem to be having with parrotbug is in sending messages. Since one needs to be online to send messages (if and when it works) why not let people just use [EMAIL PROTECTED] Then we can reserve the parrotbug program for generating bug reports offline for later reporting

Re: [perl #41601] [BUG] parrotbug b0rken

2007-03-18 Thread chromatic
On Sunday 18 March 2007 10:38, Paul Cochrane via RT wrote: > The main problem people seem to be having with parrotbug is in sending > messages. Since one needs to be online to send messages (if and when > it works) why not let people just use [EMAIL PROTECTED] Then > we can reserve the parrotbug

Re: [perl #41601] [BUG] parrotbug b0rken

2007-03-18 Thread Nicholas Clark
On Sun, Mar 18, 2007 at 06:51:32PM +0100, Paul Cochrane wrote: > parrotbug also has the save option, and it saves a lot of > configuration information. I'm asking if the "send" feature can be > removed, which is the bit which seems to be broken. We could always > revisit having a "send" feature f

Re: [perl #41601] [BUG] parrotbug b0rken

2007-03-18 Thread Paul Cochrane
On 18/03/07, Jerome Quelin <[EMAIL PROTECTED]> wrote: when i wrote parrotbug, i mimicked a lot perlbug. and iirc, there's an option --send to send the report. and if no option provided, it will prompt you on what you want to do next... so, if sending the report fails, maybe parrotbug should defa

[perl #41900] [PATCH] 2 refactor src/library.c to reduce complexity, eliminate duplicated code

2007-03-18 Thread Paul Cochrane via RT
Applied in r17628. Thanks!