Parrot 4.3.0 "In Which..." Released!

On behalf of the Parrot team, I'm proud to announce Parrot 4.3.0, also known as "In Which...". Parrot (http://parrot.org/) is a virtual machine aimed at running all dynamic languages. Parrot 4.3.0 is available on Parrot's FTP site (ftp://ftp.parrot.org/pub/parrot/releases/stable/4.3.0/), or by f

Parrot 3.11.0 "Duct Tape" Released

hanks to all our contributors for making this possible: Alekssasho, Alvis Yardley, Andrew Whitworth, Andy Lester, Brian Gernhardt, Bruce Gray, Christoph Otto, Francois Perrad, jkeenan, Jonathan "Duke" Leto, Michael Schroeder, Moritz Lenz, Nolan Lum, NotFound, Paweł Nowak, Peter Polacik, Sas

Parrot is a foundering project on top of a wonderful vision.

masak made the offhand remark in #perl6 recently that I used as the title of this message. Now that I'm done giving State of the Parrot talks, I'm free to take off my optimist hat and realize that Parrot is going to die a slow death if we don't do something drastic. I love the vision that Parrot ha

Parrot Developer Summit Q1 2011 Scheduling

Hi all, The next PDS is coming up soon. I've set up a Doodle[1] to find the best time for everyone. Please fill out your availability in the next few days if you're interested in attending. This will be a strategic planning session for Parrot, so folks from projects that build on Parrot (especi

Parrot 3.5.0 "Menelaus" Released!

930fc02d37de8953db9 parrot-3.5.0.tar.gz Many thanks to all our contributors for making this possible, and our sponsors for supporting this project. The following people (in random order) contributed to this release. Thanks! François Perrad, Bob Kuo, Jim Keenan, Bruce Gray, Gerd Pokorra, Christoph

RE: Parrot Developer Summit Q1 2011 date

a448d -Original Message- From: parrot-dev-boun...@lists.parrot.org [mailto:parrot-dev-boun...@lists.parrot.org] On Behalf Of James E Keenan Sent: Wednesday, May 04, 2011 05:55 To: Christoph Otto Cc: parrot-us...@lists.parrot.org; perl6-compi...@perl.org; parrot-...@lists.parrot.org; perl6-us...@per

Parrot Developer Summit Q1 2011 date

Hi all, Thanks to those who filled out the doodle to indicate your availability for the next Parrot Developer Summit. The slots with the fewest conflicts were at the same time on different weeks. I've closed the doodle poll and marked Saturday the 14th at 1PM UTC as the official date for the

Parrot 3.0.0 "Beef Stew" Released

oogle for sponsoring GCI and providing us with a small army of energetic and highly capable minions. Andrew Whitworth, Andy Dougherty, Andy Lester, Bob Rogers, Christoph Otto, Daniel Arbelo, Daniel Kang (gci), Daniel Toma, David Czech (gci), Fernando Brito (gci), François Perrad, Gerd Pokorra

Parrot 2.9.1 Released

On behalf of the Parrot team, I'm proud to announce Parrot 2.9.1. Parrot (http://parrot.org/) is a virtual machine aimed at running all dynamic languages. Parrot 2.9.1 is available on Parrot's FTP site, or by following the download instructions at http://parrot.org/download. For those who would

Parrot 2.0 Released!

"I can't understand why people are frightened of new ideas. I'm frightened of the old ones.” - John Cage On behalf of the Parrot team, I'm proud to announce Parrot 2.2.0 "Like Clockwork." Parrot (http://parrot.org/) is a virtual machine aimed at running all dynamic languages. Parrot 2.2.0 is

Parrot 1.4.0 "Mundo Cani" Released!

"Look at the skies," whispered the Dog kindly. "Look at the trees where God made beauty. But it is only a sorrow to look on me where God planted ugliness." sighed the Dog, "such a fine small beak you have." Not his most piercing, his most murderous crow could move this remarkable rag. Not th

Re: [perl #40002] TGE Refactor / Compiler Tools Object

Will Coleda wrote: On Sun, Jul 19, 2009 at 10:50 PM, Christoph Otto via RT wrote: On Sun Jul 19 16:18:01 2009, jk...@verizon.net wrote: Would any of the participants in this thread be able to post an update? Was the TGE refactor ever done? If not, is it still needed in light of subsequent

Re: [perl #48014] [DEPRECATED] PMC union struct

Bernhard Schmalhofer via RT wrote: Christoph Otto schrieb: Christoph Otto via RT wrote: The attached patch implements this behavior and fixes two core PMCs that had been doing the inheritance manually. All tests in make test pass. I didn't bother testing any HLLs as this is more

Re: [perl #48014] [DEPRECATED] PMC union struct

Christoph Otto via RT wrote: Allison Randal via RT wrote: Parent and child had to have the same struct in the original (because every PMC defined the same union val struct), and so still have to have the same struct in the new version. It is progress: at least the struct members will have

Re: [perl #48014] [DEPRECATED] PMC union struct

Allison Randal via RT wrote: Christoph Otto wrote: The PMC UnionVal deprecation can't be completed until Parrot has improved ATTR reuse between extending PMCs. I'm rewriting code to minimize dependence on the PMC_x_val macros, but I can't eliminate them completely without bet

Re: [perl #48014] [DEPRECATED] PMC union struct

Allison Randal via RT wrote: Christoph Otto wrote: Allison Randal wrote: (Actually, at the moment you're required to declare all parent attributes in the ATTR list before the child attributes, so inherited attributes *are* child attributes.) When I say "attributes", I mean the

Re: [perl #48014] [DEPRECATED] PMC union struct

Allison Randal wrote: Christoph Otto via RT wrote: I'm running into a snag trying to implement this. It turns out that many lines which use the PMC_x_val macros use them on different types of PMCs, especially parents and children (e.g. FixedPMCArray and ResizablePMCArray). There are also

Re: [perl #48014] [DEPRECATED] PMC union struct

Christoph Otto via RT wrote: I'm running into a snag trying to implement this. It turns out that many lines which use the PMC_x_val macros use them on different types of PMCs, especially parents and children (e.g. FixedPMCArray and ResizablePMCArray). There are also some instances wher

Re: [perl #59810] [PATCH] store hash seed in parrot_string_t struct

Christoph Otto wrote: I'd appreciate comments or a quick code review as to whether I should apply the patch as-is (sans randomization) once the failing OrderedHash test passes. It's admittedly not a complete solution, but it does hide Parrot's hash seed from any PARROT_EXPOR

Re: [perl #59810] [PATCH] store hash seed in parrot_string_t struct

Christoph Otto wrote: Nicholas Clark wrote: On Sun, Nov 16, 2008 at 06:52:08PM -0800, chromatic wrote: I'd rather remove the hash seed from the key calculation. Instead, let's use a global seed (#defined somewhere) as the initial seed, cache the calculated You don't

Re: [perl #60600] [PATCH] rewrite of ops.t to PIR

Christoph Otto via RT wrote: On Sun Nov 16 19:47:36 2008, stockwellb wrote: rewrite of t/oo/ops.t to PIR. ops.t | 265 -- 1 file changed, 130 insertions(+), 135 deletions(-) In op_get_class_p_p, it looks like you switch from

Re: [perl #59810] [PATCH] store hash seed in parrot_string_t struct

Nicholas Clark wrote: On Sun, Nov 16, 2008 at 06:52:08PM -0800, chromatic wrote: I'd rather remove the hash seed from the key calculation. Instead, let's use a global seed (#defined somewhere) as the initial seed, cache the calculated You don't want a constant global seed, else you fall fou

[perl #59940] [patch] convert perl tests to parrot

On Thu Oct 23 01:38:59 2008, mgrimes wrote: > Christoph, > > Thanks for your help. This has been a great, low intensity, way to > learn a bit of parrot. > I think I have addressed everything, and I have attached a new patch. > > > The patch no longer applies cleanly to objects.t, and I thought >

Re: [perl #59940] [patch] convert perl tests to parrot

pply cleanly. I had to make some changes to the $Id: line in the patch by hand. -Mark On Fri, Oct 17, 2008 at 10:35 AM, Mark Grimes <[EMAIL PROTECTED]> wrote: On Fri, Oct 17, 2008 at 12:39 AM, Christoph Otto via RT <[EMAIL PROTECTED]> wrote: You can fix the foo_error_bar tests by usin

[perl #59686] [CAGE] Review t/pmc/ro.t - improve error testing

On Tue Oct 07 06:53:58 2008, [EMAIL PROTECTED] wrote: > In fixing the Complex PMC in r31749, I revealed a problem in our > read-only PMC tests. In t/pmc/ro.t, test 5 gets an error as expected, > but the error it gets complains that add_p_ic_p doesn't exist (it hasn't > existed for years, if ever

[perl #59940] [patch] convert perl tests to parrot

On Thu Oct 16 17:43:28 2008, mgrimes wrote: > Hi, > > The attached patch converts two perl based tests into parrot tests: > > t/pmc/string.t > t/pmc/objects.t > > Each of these included "pir_error_is" type tests. I am not aware of > any way to test those within parrot right now, so I kept th

Re: [perl #46821] [RFC] should readonly be deep or shallow?

Will Coleda via RT wrote: On Wed Oct 24 13:52:33 2007, pcoch wrote: In t/src/ro.t there is the todo item: # XXX: should this work? and the related pir code: # three = 4 # should fail -- is that what we want The question is: is the behaviour encapsulated in the test actually what we want? T

[perl #52778] [RFC] Are resizable arrays too Perlish?

On Sun Sep 14 13:43:15 2008, cotto wrote: > On Sun Sep 14 07:47:34 2008, pmichaud wrote: > > On Sun, Sep 14, 2008 at 12:41:42AM -0700, Christoph Otto via RT wrote: > > > > > > I got impatient and committed this as r31101. I'm marking this > > ticket >

[perl #44457] [TODO] make sure files match test files for DYNPMCs and DYNOPs etc

On Mon Oct 13 07:31:30 2008, [EMAIL PROTECTED] wrote: > Hi Christoph, > > I send you the patch atached. > > The script with TODO block works equal without it(with TODO > gives more information and adds the "not yet implemented" leyend). > > Sincerely, > > Igor Hi Igor, This patch looks good.

[perl #52478] [BUG] unwanted string -> int conversion for array-like PMCs

On Tue Apr 08 19:11:10 2008, pmichaud wrote: > On Fri, Apr 04, 2008 at 02:15:26PM -0700, Christoph Otto (Volt) wrote: > > When running the following PIR code, Parrot does the Perlish thing > > and implicitly converts s to an int. This violates the principle > > of least

[perl #59782] [PATCH] add pmc_cmp VTABLE function

On Sat Oct 11 05:07:25 2008, [EMAIL PROTECTED] wrote: > Christoph Otto (via RT) wrote: > > > > In response to a question about comparison operators in Pipp*, > Allison > > suggested that I add a variant cmp VTABLE function which returns a > PMC instead > > of a

[perl #59340] t/stm/runtime_4.pir segfaults on FreeBSD 7 (i386)

On Thu Sep 25 15:09:30 2008, geraud wrote: > I reported a problem on IRC yesterday and was prompted to file a bug. >So here we go. The GeJ reports that this test is passing now so I'm marking this ticket resolved.

Re: [perl #44457] [TODO] make sure files match test files for DYNPMCs and DYNOPs etc

[EMAIL PROTECTED] via RT wrote: --- El mar 30-sep-08, Christoph Otto <[EMAIL PROTECTED]> escribió: De:: Christoph Otto <[EMAIL PROTECTED]> Asunto: Re: [perl #44457] [TODO] make sure files match test files for DYNPMCs and DYNOPs etc A: "Igor ;" <[EMAIL PROTECTED]>

Re: [perl #44457] [TODO] make sure files match test files for DYNPMCs and DYNOPs etc

Igor wrote: Hi Christoph, I send you the patch attached. Sincerely, Igor Hi Igor, Thanks again for taking the time to contribute. Here are some pointers: First, you're trying too hard. I'm sorry to tell you that after you've spent so much effort, but this change should be fairly minimal.

[perl #59336] [BUG] Parrot fails integer comparisons when integers are > 2^31 apart

On Thu Sep 25 14:18:40 2008, julianalbo wrote: > > I suspect the problem is that the integer "greater than" operation > > is performing a subtraction between the two (signed long) values > > being compared, but the result of the subtraction is outside of > > the range of signed longs. > > Correct.

[perl #50908] [CAGE] gcc -Werror=declaration-after-statement

On Wed Sep 24 10:47:16 2008, cotto wrote: > On Mon Feb 18 18:07:43 2008, coke wrote: > > On Feb 18, 2008 8:39 PM, chromatic <[EMAIL PROTECTED]> wrote: > > > On Friday 15 February 2008 11:35:04 Will Coleda wrote: > > > > > > > According to http://gcc.gnu.org/onlinedocs/index.html#DIR, looks like > >

[perl #50908] [CAGE] gcc -Werror=declaration-after-statement

On Mon Feb 18 18:07:43 2008, coke wrote: > On Feb 18, 2008 8:39 PM, chromatic <[EMAIL PROTECTED]> wrote: > > On Friday 15 February 2008 11:35:04 Will Coleda wrote: > > > > > According to http://gcc.gnu.org/onlinedocs/index.html#DIR, looks like > > > as of gcc 4.2.3 (but not 4.1.2), we can use the f

[perl #46677] [TODO] [C] Merge fixedbooleanarray.pmc with functions from BigInt PMC

On Mon Oct 22 09:47:52 2007, pcoch wrote: > In src/pmc/fixedbooleanarray.pmc there is the todo item; > > * TODO merge this with functions from BigInt PMC > > The functionality in this file should be merged with that in the BigInt PMC I propose to reject this ticket. Reducing code duplication is

[perl #57728] [TODO] avoid 2038 bug if we haven't already.

On Thu Aug 07 14:20:11 2008, coke wrote: > Open a ticket for TODO item. > > -- Forwarded message -- > From: jerry gay <[EMAIL PROTECTED]> > Date: Thu, Aug 7, 2008 at 4:34 PM > Subject: Re: time op inconsistent on Win32 > To: Ron Blaschke <[EMAIL PROTECTED]> > Cc: Jonathan Worthingt

[perl #58796] [CAGE] src/library.c (and others?) refer to .past files, which are no longer used

On Fri Sep 12 10:06:01 2008, [EMAIL PROTECTED] wrote: > src/library.c (and others?) refer to .past files, which are no longer > used. remove all references to this filetype from the parrot repo. > ~jerry This one should be closeable as of r31284. I tried acking through all instances of the strin

[perl #58866] calling a PIR sub with 206 params segfaults parrot

On Thu Sep 18 08:52:10 2008, julianalbo wrote: > I changed the fix in r31230 to allocate char instead of char *, > adjusted the formula for buffer size and added a comment explaining it > to lower the level of black magic, and added a check for each item, > dropping the XXX comment that asked for i

[perl #45909] [TODO] Replace quadratic search with something linear in find_exception_handler()

On Wed Sep 17 16:57:06 2008, cotto wrote: > On Mon Oct 01 10:40:33 2007, pcoch wrote: > > In src/exceptions.c there is the todo comment: [TODO: replace > > quadratic search with something linear, hopefully without trashing > > abstraction layers > > > I can't find this comment any more, nor any o

[perl #45909] [TODO] Replace quadratic search with something linear in find_exception_handler()

On Mon Oct 01 10:40:33 2007, pcoch wrote: > In src/exceptions.c there is the todo comment: [TODO: replace > quadratic search with something linear, hopefully without trashing > abstraction layers I can't find this comment any more, nor any occurrence of this ticket's number. I'll do some digging

[perl #58866] calling a PIR sub with 206 params segfaults parrot

On Wed Sep 17 08:31:26 2008, particle wrote: > On Tue, Sep 16, 2008 at 11:45 PM, Christoph Otto via RT > <[EMAIL PROTECTED]> wrote: > > On Tue Sep 16 15:00:24 2008, [EMAIL PROTECTED] wrote: > >> On Tuesday 16 September 2008 14:47:58 NotFound wrote: > >> >

[perl #41291] [RFC] Can't use null PMC with :multi sub

On Thu Jan 18 14:14:30 2007, mdiep wrote: > On Thu Jan 18 13:52:33 2007, leo wrote: > > While that was never actually specced, I do consider a NULL PMC as > > something > > like a null pointer in C. Any access (except testing for NULL-ness) > to > > it is > > an error. Above example tests, that som

[perl #54110] [BUG] segfault in infix/n_infix with string arguments

On Tue Sep 09 15:06:38 2008, [EMAIL PROTECTED] wrote: > Patrick R. Michaud wrote: > > > > Just for clarification: IIUC, the n_* opcodes and their semantics > > aren't really "going away" -- they're simply being renamed to not > > have the leading "n_" prefix. It's the existing "add", "sub", >

[perl #58866] calling a PIR sub with 206 params segfaults parrot

On Tue Sep 16 15:00:24 2008, [EMAIL PROTECTED] wrote: > 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

[perl #53536] [PATCH] sub-second sleep precision for non-threaded architectures

On Mon Sep 15 20:08:38 2008, [EMAIL PROTECTED] wrote: > chromatic wrote: > > On Monday 15 September 2008 01:25:15 Christoph Otto via RT wrote: > > > >> It applies with a little noise to the current trunk and passes make > >> test. The attached version just

Re: [perl #46681] [TODO] [C] Use strerror_r instead of strerror

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

[perl #52778] [RFC] Are resizable arrays too Perlish?

On Thu Sep 11 23:15:50 2008, cotto wrote: > On Mon Sep 08 22:54:28 2008, [EMAIL PROTECTED] wrote: > > Patrick R. Michaud wrote: > > > > > > Fixing this shouldn't be all that difficult -- in particular, > > > I think that src/pmc/resizablepmcarray.pmc lines 205-206 should > > > be changed from > > >

[perl #49722] [CAGE] Add Tests for SchedulerMessage PMC

On Sun Jan 13 05:38:42 2008, coke wrote: > > > -- > Will "Coke" Coleda > > On Jan 12, 2008, at 7:33 PM, chromatic (via RT) [EMAIL PROTECTED] > > wrote: > > > # New Ticket Created by chromatic > > # Please include the string: [perl #49722] > > # in the subject line of all future corresponden

Re: [perl #46681] [TODO] [C] Use strerror_r instead of strerror

After looking around Parrot and realizing that there were several other places where strerror is used, I'm trying a different approach. The attached patch adds config/gen/platform/generic/strerror.c, which contains a new function Parrot_strerror. This is just a wrapper to abstract away the non

[perl #52778] [RFC] Are resizable arrays too Perlish?

On Mon Sep 08 22:54:28 2008, [EMAIL PROTECTED] wrote: > Patrick R. Michaud wrote: > > > > Fixing this shouldn't be all that difficult -- in particular, > > I think that src/pmc/resizablepmcarray.pmc lines 205-206 should > > be changed from > > > > - if (key >= PMC_int_val(SELF)) > > -

Re: [perl #46681] [TODO] [C] Use strerror_r instead of strerror

Will Coleda via RT wrote: On Tue Jul 22 23:34:13 2008, [EMAIL PROTECTED] wrote: Christoph Otto via RT wrote: This version of the patch should dtrt with all versions of strerror_r. It works on my Debian/x86 box and I'll be testing it on any *nix I can get my hands on Tuesday. If it

[perl #44457] [TODO] make sure files match test files for DYNPMCs and DYNOPs etc

On Mon Aug 06 06:08:54 2007, pcoch wrote: > In the file t/distro/test_file_coverage.t there is the todo item: > > # TODO: DYNPMC, DYNOPS, etc > > This is in the context of making sure that the files match the test > files. This needs to be implemented. Is this as simple as writing a test to mak

[perl #55372] [BUG] Segfault/double free when manually running "perl6"

On Sun Sep 07 15:19:22 2008, cotto wrote: > 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 ex

[perl #41825] [BUG] morph vtable override not working in PIR

On Tue Nov 20 20:58:35 2007, [EMAIL PROTECTED] wrote: > On Wed Mar 14 07:49:33 2007, [EMAIL PROTECTED] wrote: > > Hi, > > > > Given the following: > > > > .namespace ['A'] > > > > .sub 'morph' :method :vtable > > say 'morphing!' > > .end > > > > .sub main :main > > $P0 = newclass 'A' >

[perl #41892] [BUG] t/stm/llqueue segment violation on test #2

On Mon Mar 19 10:22:42 2007, coke wrote: > test TODOd for next release, thanks for the report. > > (Hopefully it'll get fixed shortly after the release.) > > On Sun Mar 18 08:07:05 2007, [EMAIL PROTECTED] wrote: > > I get SIGSEGV in t/stm/llqueue, test #2 > > > > openSuSe 10.2 linux 2.6.18.8-0.

Re: [perl #52778] Are resizable arrays too Perlish?

Patrick R. Michaud wrote: Fixing this shouldn't be all that difficult -- in particular, I think that src/pmc/resizablepmcarray.pmc lines 205-206 should be changed from - if (key >= PMC_int_val(SELF)) - SELF.set_integer_native(key+1); to something like + if (key >= PMC_

[perl #46651] [TODO] [C] Make a better interface for hash creation

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?

[perl #46635] [TODO] [C] Check overflow for -maxint in absolute()

On Thu Feb 21 12:15:06 2008, Whiteknight wrote: > What would be the best way to handle this? We certainly don't need to do > anything on systems where INT_MAX == -INT_MIN, but a simple compiler > directive should help to detect that case. > > In the event that abs(INT_MIN) > abs(INT_MAX), should

[perl #45357] [TODO] Which exception should be thrown with register overflow?

On Tue Sep 11 03:32:51 2007, pcoch wrote: > Having a look through PDD03 I noticed the TODO item left by Chip: > > =head3 Overflow > > If too many values are provided to fit into the given target > registers, Parrot > will throw an exception. Note that if the final target is a P > register

[perl #42378] [TODO] explicit exit from debug_break() op is not ok

On Mon Apr 09 01:29:52 2007, pcoch wrote: > In the file src/ops/debug.ops in the debug_break() op, there is an > explicit exit(0), which is marked as being not an ok thing to do. > This issue needs to be investigated and fixed. It looks like the explicit exit in debug_break() is gone, so I'm marki

[perl #54938] [BUG] Double free

On Fri Sep 05 12:16:25 2008, cotto wrote: > On Tue May 27 13:33:11 2008, [EMAIL PROTECTED] wrote: > > Running this program: > > > > sub foo($a) {say $a} ; my $x = ; > > > > on Ubuntu 8.04 with latest Parrot from svn gives this: > > > > $ ./perl6 test.p6 > > Statement not terminated properly

[perl #58484] [PATCH] Use of uninitialized value in scalar assignment at lib/Parrot/Revision.pm line 95.

On Mon Sep 08 04:23:37 2008, [EMAIL PROTECTED] wrote: > Applied in r30888. cotto is going to check its functioning on Cygwin, > but it did no harm on Darwin and Linux, so I'm committing it now. > > Thank you very much. > kid51 It looks good on Cygwin too, so I'm marking this resolved.

[perl #56636] [BUG] segfault from sort if comparison is always 1

On Mon Jul 07 00:13:20 2008, [EMAIL PROTECTED] wrote: > On Sunday 06 July 2008 22:17:12 Andrew Johnson via RT wrote: > > > On Sun Jul 06 11:03:37 2008, japhb wrote: > > > > Better yet, we should replace the inherently insecure quicksort > > > algorithm (insecure in the "vulnerable to algorithmic

[perl #52054] [CAGE]: Make all PDDs conform to coding standards

On Mon Sep 08 00:12:44 2008, cotto wrote: > On Mon Sep 08 00:01:08 2008, [EMAIL PROTECTED] wrote: > > Christoph Otto wrote: > > > > > > If those are your thoughts on the subject, then it seems to make sense > > > to add the pdd format test to make test. The

[perl #51464] [TODO] [PDD] add date stamps to PDD's

On Mon Sep 08 01:18:37 2008, [EMAIL PROTECTED] wrote: > Christoph Otto via RT wrote: > > > > Is this something we want to go ahead with or should this ticket be > > rejected? > > I've had it on my hiveminder todo list for over a month now. The problem > is,

[perl #52054] [CAGE]: Make all PDDs conform to coding standards

On Mon Sep 08 00:01:08 2008, [EMAIL PROTECTED] wrote: > Christoph Otto wrote: > > > > If those are your thoughts on the subject, then it seems to make sense > > to add the pdd format test to make test. The attached patch does this. > > I'll apply it and mark th

[perl #57668] [BUG][PATCH] Iterate through the current namespace causes a segfault

On Fri Sep 05 00:18:19 2008, [EMAIL PROTECTED] wrote: > Bob Rogers wrote: > >From: chromatic <[EMAIL PROTECTED]> > > > >Fixed in r30286. > > > >-- c > > > > Terrific; thanks. (Especially since it looks like something I may > have > > seen in other circumstances, but could not reproduce

[perl #55372] [BUG] Segfault/double free when manually running "perl6"

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

[perl #39117] [TODO] Using v?snprintf/strlcpy/strlcat when useful

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

[perl #57610] [PATCH] Resumable exceptions

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

[perl #58374] [TODO][PDD19] Decide on maximum identifier length and implement this.

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

[perl #56614] [TODO] Config hash should be marked read-only

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

[perl #39430] [TODO] Method cache not always invalidated

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

[perl #40156] [TODO] - Can't use an Iterator with a DynLexPad PMC

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

[perl #48320] [BUG] Example in pdd23 doesn't work

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

Re: [perl #52054] [CAGE]: Make all PDDs conform to coding standards

Allison Randal via RT wrote: Christoph Otto wrote: The non-draft PDDs are all passing t/codingstd/pdd_format.t as of r30810, but two of the draft PDDs aren't. Since they're still drafts and as such are very likely to change, it doesn't seem worthwhile to bring them into compli

Re: [PATCH] added links to dotnet/doc/contents.pod

Reini Urban wrote: Attached patch adds links to external dotnet ressources Jonathan mentioned (his paper, the specs), and the implementations. Jonathan should approve it because it links to a bad poem on VM's in his paper on page 1. No ticket because it's so simple. Thanks. This was applied

[perl #51464] [TODO] [PDD] add date stamps to PDD's

On Fri Apr 04 16:52:39 2008, [EMAIL PROTECTED] wrote: > On Fri Apr 04 04:30:17 2008, [EMAIL PROTECTED] wrote: > > > One (possibly solvable) problem is that subversion tags don't > > substitute properly in the HTML generated versions on the website > >

[perl #48320] [BUG] Example in pdd23 doesn't work

On Sat Feb 16 17:23:47 2008, coke wrote: > The example in the PDD now reads: > > $P0 = new 'String' > $P0 = "something bad happened" > $P1 = new ['parrot';'exception'], $P0 # create new exception object > throw $P1 # throw it > This code continues to not wo

[perl #48971] [BUG] Parrot build failure "no such instruction: `trap'"

On Sun May 04 03:11:12 2008, [EMAIL PROTECTED] wrote: > Excellent, the patch from ticket 52214 works. > > Walter > resolved

[perl #54110] [BUG] segfault in infix/n_infix with string arguments

On Tue May 13 08:05:08 2008, coke wrote: > On Tue, May 13, 2008 at 9:48 AM, via RT Patrick R. Michaud > <[EMAIL PROTECTED]> wrote: > > # New Ticket Created by Patrick R. Michaud > > # Please include the string: [perl #54110] > > # in the subject line of all future correspondence about this > is

[perl #54414] [BUG] t\benchmark\benchmarks.t failure (r27624)

On Mon May 19 03:55:46 2008, [EMAIL PROTECTED] wrote: > On Sun May 18 17:02:30 2008, ajr wrote: > > t\benchmark\benchmarks..28/37 > > # Failed test 'examples/benchmarks/primes2.pasm' > > # at t\benchmark\benchmarks.t line 219. > > # Exited with error code: 1 > > I think this problem is not

[perl #48172] [TODO] [pugs] Getting nonexistent value, exception or undef?

On Wed Dec 05 04:49:22 2007, pcoch wrote: > In languages/pugs/pmc/pugscapture.pmc:retval() there is the todo item: > > /* XXX getting non existent value, exception or undef? > > It looks like we need to determine at this point whether or not the value > we are getting doesn't exist, is an except

[perl #52854] [bug] Build failure with G++

On Mon Apr 14 08:07:32 2008, [EMAIL PROTECTED] wrote: > On Mon, Apr 14, 2008 at 11:40:01AM +0530, Senaka Fernando wrote: > > > On Mon, Apr 14, 2008 at 6:33 AM, chromatic <[EMAIL PROTECTED]> > wrote: > > > > Thanks, applied as r26965, except for the patch to > > > compilers/imcc/imclexer.c, which

[perl #55196] [BUG] print/say opcodes have different float precision

On Mon Jun 02 13:08:27 2008, [EMAIL PROTECTED] wrote: > 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]:

[perl #54938] [BUG] Double free

On Tue May 27 13:33:11 2008, [EMAIL PROTECTED] wrote: > Running this program: > > sub foo($a) {say $a} ; my $x = ; > > on Ubuntu 8.04 with latest Parrot from svn gives this: > > $ ./perl6 test.p6 > Statement not terminated properly at line 1, near "= ;\n" > current instr.: 'parrot;PGE::Util

[perl #50878] [BUG] is_equal vtable function not callable in C

On Fri Feb 15 02:43:05 2008, [EMAIL PROTECTED] wrote: > > They're marked as MMD in vtable.tbl, so my guess is that they're not > directly > callable by vtable pointer from C. F (though admittedly > out of > date) suggests that mmd_dispatch_* is the right approach. > > -- c > Sounds good enough

[perl #32087] [PATCH] .include with an absolute path

On Fri Sep 05 00:58:51 2008, cotto wrote: > On Fri Aug 01 06:44:05 2008, coke wrote: > > On Thu, Jul 31, 2008 at 7:35 PM, James Keenan via RT > > <[EMAIL PROTECTED]> wrote: > > > Coke: Given the points Leo made and the fact that there has been > > > nothing from the OP in 4 years, can we close thi

[perl #48176] [TODO] [pugs] Warning: use of uninitialized value

On Wed Dec 05 04:53:15 2007, pcoch wrote: > In languages/pugs/pmc/pugscapture.pmc there are todo items of the form: > > /* XXX Warning: use of uninitialized value */ > > This looks very similar to RT#48170 which was in the regex language. Does > this todo item mean that we should be *warning* ab

[perl #48439] [TODO] [configure] compiling Parrot with LLVM

On Mon Dec 10 08:52:27 2007, [EMAIL PROTECTED] wrote: > Marton Papp has successfully compiled Parrot with LLVM on Windows with > mingw-make (it's failing 18 tests, which is impressively low for a first > run on a new compiler). Below is his summary of the steps he followed. > I'd like to extract

[perl #51838] [BUG] cygwin build fails

On Tue Mar 18 14:05:34 2008, rurban wrote: > > It's time to use Configure.pl with the option --without-crypto > > Or to add -lcrypto to the cmdline. > Configure.pl fails to pick it up apparently. > > my %Parrot::Config::Generated::PConfig contains -lcrypto in libs > 'libs' => '-ldl -lcrypt -lgm

[perl #52976] [BUG] perl6 stand-alone binary broken

On Wed Apr 16 14:24:28 2008, [EMAIL PROTECTED] wrote: > On Wednesday 16 April 2008 10:49:15 Christoph Otto (Volt) wrote: > > > The perl6 stand-alone binary chokes on chromatic's mmd example > > > (http://www.oreillynet.com/onlamp/blog/2008/04/multiple_dispatch_now_please

Re: [perl #52054] [CAGE]: Make all PDDs conform to coding standards

James Keenan via RT wrote: The PDDs in docs/pdds/ are now in substantial compliance with the coding standard, those in docs/pdds/draft/ much less so. I'll leave this ticket open, but it's the sort of thing that only needs some cage cleaning attention every month or so. The non-draft PDDs are

[perl #57116] [BUG] make: *** [perl6] Segmentation fault

On Tue Jul 29 00:38:29 2008, tuxdna wrote: > I found that it is now working correctly in the latest revision 29838. resolved

[perl #39313] [TODO] or [BUG] improve PMC compiler

On Fri Jun 27 13:14:53 2008, coke wrote: > > While I think this particular example is now valid with the new calling > conventions, you can get a similar effect with: > > METHOD BORK BORK parent() { > /* nothing to see here*/ > } This ticket doesn't seem to be closeable as is. Would it be goo

[perl #56304] smokej consumes all memory Revision: 28672 on linux

On Mon Jul 14 13:47:29 2008, [EMAIL PROTECTED] wrote: > Seems to be fixed as of 29440: Sounds like a happy ending. resolved

[perl #32087] [PATCH] .include with an absolute path

On Fri Aug 01 06:44:05 2008, coke wrote: > On Thu, Jul 31, 2008 at 7:35 PM, James Keenan via RT > <[EMAIL PROTECTED]> wrote: > > Coke: Given the points Leo made and the fact that there has been > > nothing from the OP in 4 years, can we close this ticket? > > > > Thanks. > > > > kid51 > > > > Jus

  1   2   >