Committer Reminder: Please Check RT
We have some 845 open tickets in RT, which is approximately 840 more than I'd like to see at any one time. I closed a dozen or so today. If every active committer could close one or two every week, we'd make real progress very shortly. The Bug Summary lists new issues to which no one has responded. Many of these are easy fixes: http://rt.perl.org/rt3/NoAuth/parrot/Overview.html Plenty of tickets in the open patches list need verification -- many are closeable if you can only verify that someone has applied them: http://rt.perl.org/rt3/NoAuth/parrot/List.html?Field=TagValue=Patch The full queue remains available: http://rt.perl.org/rt3/Search/Results.html?Query=Queue%20%3D%20'parrot'%20AND%20 (Status%20%3D%20'open'%20OR%20Status%20%3D%20'new'%20OR%20Status%20%3D%20'stalled') A ten-minute investment here can help us greatly! -- c
Re: [perl #51380] [PATCH] Code layout of imcc.y
chromatic via RT schrieb: i. rule names start at pos 0. The colon follows immediately. Nothing else is on that line. ii. productions start a pos 5 iii. the '|' separating productions is at pos 3 iv. the semicolon finishing a rule is at pos 3 v. actions are either inline or start at pos 10 vi. inline actions preferable start at pos 27 A patch of imcc.y is attached. All test of 'make test' are passing. Could somebody with 'yacc' experience comment? Great idea. Unfortunately, I ran into a collision in hunk #6, starting at line 861. Can you rebase and resubmit? (Or apply yourself, that's fine too.) -- c In order to play it safe, I'll rebase and apply after the Parrot 0.6.0 release.
Re: [svn:perl6-synopsis] r14520 - doc/trunk/design/syn
On Sat, Mar 15, 2008 at 06:09:40PM -0700, [EMAIL PROTECTED] wrote: Author: larry Date: Sat Mar 15 18:09:39 2008 New Revision: 14520 @@ -1367,9 +1367,10 @@ If you need to force inner context to scalar, we now have convenient single-character context specifiers such as + for numbers and ~ for strings: +$x= g(); # scalar context and g() s/and/for/ in this last line, I think. -- I think you look like the Mona Lisa. You always seem to be at a window admiring the landscape that is actually behind you.Herve Le Tellier http://surreal.istic.org/ Habit is a good slave but a poor master. signature.asc Description: Digital signature
[perl #51758] [BUG] Segfault for 'alarm' op in computed-goto runcore
# New Ticket Created by Bernhard Schmalhofer # Please include the string: [perl #51758] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=51758 Hi, when runnung 'make fulltest' I noticed a segfault for the 'alarm' op. It occurs only the '-g' runcore. [EMAIL PROTECTED]:~/devel/Parrot/trunk$ ./parrot -b t/dynoplibs/myops_6.pir alarm1 alarm2 alarm3 [EMAIL PROTECTED]:~/devel/Parrot/trunk$ ./parrot -g t/dynoplibs/myops_6.pir Segmentation fault (core dumped) [EMAIL PROTECTED]:~/devel/Parrot/trunk$ uname -a Linux heist 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~/devel/Parrot/trunk$ gcc --version gcc (GCC) 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) Copyright (C) 2006 Free Software Foundation, Inc. Dies ist freie Software; die Kopierbedingungen stehen in den Quellen. Es gibt KEINE Garantie; auch nicht für MARKTGÄNGIGKEIT oder FÜR SPEZIELLE ZWECKE. [EMAIL PROTECTED]:~/devel/Parrot/trunk$ Regards, Bernhard
[perl #51784] [PATCH] Build a TAGS file for emacs
# New Ticket Created by Matt Kraai # Please include the string: [perl #51784] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=51784 Howdy, The attached patch adds a target to build a TAGS file for emacs. It's not as featureful as the tags file for vi because I haven't modified addopstags.pl, but it is helpful. -- Matt diff --git a/config/gen/makefiles/root.in b/config/gen/makefiles/root.in index bb85014..486d6e4 100644 --- a/config/gen/makefiles/root.in +++ b/config/gen/makefiles/root.in @@ -2151,6 +2151,21 @@ $(LIBNCI_TEST_SO): $(SRC_DIR)/nci_test$(O) $(LD) $(LD_LOAD_FLAGS) @ncilib_link_extra@ $(LDFLAGS) \ @[EMAIL PROTECTED]@ $(SRC_DIR)/nci_test$(O) $(C_LIBS) +# emacs etags +# this needs exuberant-ctags + +TAGS: TAGS.dummy + $(RM_F) TAGS + @ctags@ -e \ +--links=no --totals \ +-R --exclude=blib --exclude=.svn \ +--exclude=res_lea.c \ +--languages=c,perl --langmap=c:+.h,c:+.pmc,c:+.ops \ +-I NOTNULL,NULLOK,ARGIN,ARGMOD,ARGOUT,ARGINOUT,ARGIN_NULLOK,ARGOUT_NULLOK,ARGMOD_NULLOK \ +$(CUR_DIR) + +TAGS.dummy: + # vim ctags # this needs exuberant-ctags
[perl #38262] [CAGE] get external Perl5 modules out of the parrot repo
On Sun Mar 16 05:00:30 2008, bernhard wrote: I'm reopening this ticket, as there are still external Perl 5 modules in lib/Digest, lib/File, lib/IO, lib/Pod. The Perl::Critic policies in lib/Perl/Critic/Policy seem to be Parrot-specific. Barney, I understood the point of the ticket to be to get rid of those Perl 5 modules which were part of the Perl 5 core distribution (at least as of our minimum required version, 5.8.0). So those modules that I eliminated -- e.g., Test::Builder, Test::More, Class::Struct -- were those that anyone with a typical Perl 5.8 would already have. Those that remain -- e.g., File::Which, IO::CaptureOutput -- are *non-core*. They are generally small enough that we include them in the Parrot distribution as a convenience to our users. If my understanding is correct, then we can re-close the ticket.
[perl #51752] [PATCH] Fix t/codingstd/check_isxxx.t failures
This was applied to trunk by chromatic in r26371 and r26372.
Re: [svn:perl6-synopsis] r14520 - doc/trunk/design/syn
On Sat, Mar 15, 2008 at 06:09:40PM -0700, [EMAIL PROTECTED] wrote:
@@ -1367,9 +1367,10 @@
If you need to force inner context to scalar, we now have convenient
single-character context specifiers such as + for numbers and ~ for strings:
+$x= g(); # scalar context and g()
@x[f()] = g(); # list context for f() and g()
@x[f()] = +g(); # list context for f(), scalar context for g()
-@x[+f()] = g(); # scalar context for f() and g()
+@x[+f()] = g(); # scalar context for f(), list context for g()
# -- see S03 for SIMPLE lvalues
@x[f()] = @y[g()]; # list context for f() and g()
@@ -1377,6 +1378,18 @@
@x[+f()] = @y[g()]; # scalar context for f(), list context for g()
@x[f()] = @y[+g()]; # list context for f(), scalar context for g()
+Sigils used as list prefix operators may also be used to force context:
+
+@x = $ g(); # scalar context for g()
+$x = @ g(); # list context for g()
+$x = % g(); # list context for g() (and coercion to hash)
Given the last paragraph, wouldn't the earlier example be more correctly
described as
@x[f()] = +g(); # list context for f(), number context for g()
and more general example instead be
@x[f()] = $ g(); # list context for f(), scalar context for g()
given that the obvious hash analogy of
@x[+f()] = g(); # scalar context for f(), list context for g()
is
%x{+f()} = g(); # number context for f(), list context for g()
and (if I understand context and its coercion correctly) actually that's
probably not what the novice wanted. In that what they probably wanted was
%x{~f()} = g(); # string context for f(), list context for g()
So instead of emphasising + and ~, it feels to me that that is less to
remember (and less to teach) if the examples were prominent in their use of
(generic) scalar context:
%x{$ f()} = g(); # scalar context for f(), list context for g()
Nicholas Clark
[perl #51300] [PATCH] t/perl/Parrot_Test.t fails because of incompatible Test::Builder output
This has been passing tests on my boxes and on smoke tests for several days, so I am re-closing the ticket.
Re: [perl #38262] [CAGE] get external Perl5 modules out of the parrot repo
On Sun, Mar 16, 2008 at 9:10 AM, James Keenan via RT [EMAIL PROTECTED] wrote: On Sun Mar 16 05:00:30 2008, bernhard wrote: I'm reopening this ticket, as there are still external Perl 5 modules in lib/Digest, lib/File, lib/IO, lib/Pod. The Perl::Critic policies in lib/Perl/Critic/Policy seem to be Parrot-specific. Barney, I understood the point of the ticket to be to get rid of those Perl 5 modules which were part of the Perl 5 core distribution (at least as of our minimum required version, 5.8.0). So those modules that I eliminated -- e.g., Test::Builder, Test::More, Class::Struct -- were those that anyone with a typical Perl 5.8 would already have. Those that remain -- e.g., File::Which, IO::CaptureOutput -- are *non-core*. They are generally small enough that we include them in the Parrot distribution as a convenience to our users. If my understanding is correct, then we can re-close the ticket. The original ticket was to get *all* modules that were not parrot-specific out of core. I had just pointed out that many of these were an easy win. Let's leave the ticket open for now. -- Will Coke Coleda
[perl #39823] [CAGE] tools/dev/run_indent.pl -- this should be a test
No one has spoken up in defense of tools/dev/run_indent.pl. If no one does so within 24 hours, I will yank it from the distribution and close this ticket. kid51
[perl #41165] [PATCH] appropriate handle CRLE in Here Docs
There's been no activity in this RT for more than a year, so I am resolving the ticket.
[perl #39829] [PATCH] accept() always fails
There's been no activity in this RT for 1-3/4 years, so I'm going to presume that the issues discussed have been resolved. Closing ticket.
[perl #38405] [PATCH] cleanup Makefiles for cleaning/building, plus shared for darwin
My hunch is that the files being proposed for revisions in the patch in this RT have undergone so many changes over the past two years that the patch would no longer be valid. If no one speaks up, I will close the ticket after this week's release. kid51
[perl #40830] [PATCH] Man-Chicken's awesome hackathon throw-away patches...
While I think the patches proposed in this ticket are moribund, the fact is that what little feedback we get on Cygwin indicates that many core tests are failing during smoke testing. See, e.g., http://smoke.parrotcode.org/smoke/parrot-smoke-0.5.3-devel-r26408-unknown--i386-cygwin-ccache-default--1205664735-3891--6759-6386-373-239-537-0--2d443430202d2d67632d6465627567202d2d72756e2d65786563--9ee766b1915c8ba87fa9a4685e9be46b.html
[perl #46305] [PATCH] (darwin) C parenthesis cleanup
coke made this fix last month: r25559 | coke | 2008-02-06 20:17:40 -0500 (Wed, 06 Feb 2008) | 7 lines [t] Update coding standard test so that someone looking at the verbose output knows what to fix without having to read the source of the test; makes output of the test more like that of t/distro/file_metadata.t ... and this is what I'm now getting on Darwin for this test: [parrot] 512 $ prove -v t/codingstd/c_parens.t t/codingstd/c_parens.. 1..3 ok 1 - there should be at least one space between a C # keyword and any subsequent open parenthesis # ok 2 - There should be no space between a function name # and the following open parenthesis # ok 3 - parentheses should not have space immediately # after the opening parenthesis nor immediately # before the closing parenthesis # ok All tests successful. Files=1, Tests=3, 30 wallclock secs ( 0.04 usr 0.03 sys + 15.87 cusr 0.76 csys = 16.70 CPU) Result: PASS So I'm concluding that we don't need further revisions to the test at this time. Patch not applied; resolving ticket. kid51
[perl #46927] [PATCH] Remove integer - pointer comparison in slice.pmc
Paul, Given Joshua's comments, should we still be considering this patch? Thanks. kid51
[perl #39988] [DOCS] Stackless vtable calls to Parrot functions
The issues that this thread was discussing appear to have been resolved, but the most recent posting was a request for the development of a PDD. Allison, Bob: Is this going to happen? If so, I think we should track it in a separate RT so that we close this one. If not, then I will close this ticket after this week's release. Thank you very much. kid51 On Thu Aug 03 11:59:01 2006, [EMAIL PROTECTED] wrote: Bob Rogers wrote: There's no way to get full Continuations working around such C code barriers, except by *not* entering secondary runloops at all for these cases[1]. This could be achieved by (optionally) returning a new PC for all vtable/MMD functions that is, by changing the internal (C) calling conventions of all the PMC code. I see a solution for simpler cases, that might even work for custom sort functions, though it's certainly not painless. Here's what I would like to do for calling actions: Bob, could you briefly write up the problem and proposed solution as a [PDD] ticket for the extending, embedding, and external C API PDDs (10-12, and possibly 2 and 23)? How we handle exceptions and control-flow across C/Parrot boundaries is an important question, and I want to make sure we address it. Thanks, Allison
[perl #17490] Magic is useless unless verifiable.
Jonathan: You took this RT some time back. Could you give us an update on its status? (It's the oldest outstanding RT.) Thank you very much. kid51
[perl #41619] [PATCH] add add_attr, rem_attr, and rem_attr_str vtable methods
On Mon Mar 12 05:40:14 2007, [EMAIL PROTECTED] wrote: I'm still working on my use case, but it appears the new MetaClass PMC (src/pmc/metaclass.pmc) could use this vtable method as well; currently it only has an add_attribute PMETHOD. Alek, Are you still planning work on this patch? (No activity in thread for 1 year.) Could you give us an update on the issues at hand? Thank you very much. kid51
[perl #41620] [PATCH] change opcode syntax for label arguments
On Sun Feb 25 20:12:58 2007, [EMAIL PROTECTED] wrote: This patch changes the label INT, labelvar INT, and labelconst INT syntax in opcodes to in LABEL, invar LABEL, and inconst LABEL, respectively. The argument is still an integer, however. This cuts the number of argument directions down by three, and only adds one argument type, making the code clearer. This is really an argument type, after all, not a special kind of direction. I doubt there will be any confusion about LABEL really being INT, because no ops do any arithmetic with it; they just use it for goto OFFSET($1) and goto ADDRESS($1). Files affected: languages/dotnet/ops/dotnet.ops lib/Parrot/OpsFile.pm src/ops/cmp.ops src/ops/core.ops src/ops/stm.ops There's been no activity in this thread for 1 year. While the patch did apply successfully, that was in a branch which has long since been removed. I doubt it was ever applied to trunk. Can someone who is knowledgeable about the ops re-evaluate this patch? Thank you very much. kid51
[perl #41818] [PATCH */4]: [t/op] add tests for string memory layout
Jerry, Sam: There's been no activity in this thread for 1 year. Should we still be evaluating this patch proposal? Thank you very much. kid51
[perl #41874] [PATCH] extended io_mmap implementation
chromatic, allison: Are the issues raised by this patch still relevant? (No activity in 9 months.) If not, then we should resolve the ticket. Thank you very much. kid51
[perl #42155] [PATCH] move members from Parrot_Interp to Parrot_Context
There's been no activity in this thread for 10+ months. In the last posting on Apr 24 2007, mdiep wrote: I was taking a look at this patch and tried to apply it, but it no longer applies cleanly. If you re-submit so that it applies cleanly, I'll check in if I can get all tests to pass. My guess is that the patch was never resubmitted. If so, I will close the ticket after this week's release. Speak up now, ladies and gentlemen! Thank you very much. kid51
[perl #42300] [PATCH] t/pmc/sub.t: test for creation of lex by clone op
On Sat Sep 08 07:07:13 2007, bernhard wrote: As the original issue has been clarified, can I close this ticket? Since no one has suggested otherwise since September, I'll close it for you :-) kid51
[perl #42898] [PATCH] src/library.c , honor PARROT_PREFER_SOURCE in extension guessing
Mike, Allison: Can you give us an update as to where the issues discussed in this thread stand? (No activity in thread since May 2007.) Thank you very much. kid51
[perl #42919] [BUG] and [PATCH] overriding 'invoke' requires current object to be explicitly passed
On Wed May 16 04:27:03 2007, [EMAIL PROTECTED] wrote: The results of my first post in this thread were probably caused by the fact that some files were not updated correctly (I am new to revision control). Both Allison's and Alek's patches have in fact the same effect. But the problem that I stated in my second post and the proposed solution are valid. A possible problem: could current_args get GC'd in the meantime? Never mind. When I was writing the above I was thinking as if current_args was some sort of PMC. Mehmet, Allison: Am I correct to infer that this thread can be closed? If there are any outstanding issues, perhaps they should be addressed in a new ticket. Thank you very much. kid51
[perl #43414] [PATCH] jit_emit.h changes for various platforms
On Thu Jun 28 10:26:30 2007, ptc wrote: Hi, as part of my cleaning up the usage of 'INTERP', 'Interp' and 'interpreter' to consistently use 'interp', as well as changing internal_exception()s to real_exceptions(), here are some patches affecting platforms I (unfortunately) don't have access to, so I can't test them (platforms are: hppa, ia64, ppc and arm). Could someone please apply these and test them for me? Thanks heaps in advance! Paul Paul, Since last June some of the files you were proposing to patch have changed considerably. I think the revisions proposed in src/jit/ppc/jit_emit.h have been implemented in the course of other revisions. But it looks like src/jit/arm/jit_emit.h might still benefit from your patch. Could you review these patches? Thank you very much. kid51
[perl #44363] [PATCH] -D80 + bad luck = segfault
Bram, chromatic: There's been no activity in this thread since last August. Can you give us an update on the issues at hand? Thank you very much. kid51
Re: [perl #46927] [PATCH] Remove integer - pointer comparison in slice.pmc
Jim, Given Joshua's comments, should we still be considering this patch? My guess is no. The compiler warning is probably gone by now anyway. Paul
[perl #42944] [PATCH] new parrot path handling API from static functions in src/library.c
Mike, Going through open tickets today, I noticed that there haven't been any postings in this thread since last May. Should we still be considering your patches? If so, can you try them against the current SVN head and update them as needed? Thank you very much. kid51
[perl #44795] [PATCH] IMCC compiler fixups for C++
Steve, Barney: Should we still have this patch under consideration? (No activity since last September.) Thank you very much. kid51
[perl #39988] [DOCS] Stackless vtable calls to Parrot functions
From: James Keenan via RT [EMAIL PROTECTED] Date: Sun, 16 Mar 2008 09:14:43 -0700 The issues that this thread was discussing appear to have been resolved, but the most recent posting was a request for the development of a PDD. Allison, Bob: Is this going to happen? If so, I think we should track it in a separate RT so that we close this one. If not, then I will close this ticket after this week's release. Thank you very much. kid51 I think it ought to happen, though I think Allison just wanted a ticket for updating existing PDDs, and not for a whole new PDD. I asked Allison for a clarification on 11-Mar in Will's [oops; continuation 0xb6926320 of type 22 is trying to jump from runloop 15008 to runloop 1] thread, and had been waiting for that. But I do agree that it ought to be a separate ticket. The underlying issue is still with us, but has outgrown the original ticket. -- Bob
Re: [perl #43414] [PATCH] jit_emit.h changes for various platforms
On 16/03/2008, James Keenan via RT [EMAIL PROTECTED] wrote: On Thu Jun 28 10:26:30 2007, ptc wrote: Hi, as part of my cleaning up the usage of 'INTERP', 'Interp' and 'interpreter' to consistently use 'interp', as well as changing internal_exception()s to real_exceptions(), here are some patches affecting platforms I (unfortunately) don't have access to, so I can't test them (platforms are: hppa, ia64, ppc and arm). Could someone please apply these and test them for me? Thanks heaps in advance! Paul Paul, Since last June some of the files you were proposing to patch have changed considerably. I think the revisions proposed in src/jit/ppc/jit_emit.h have been implemented in the course of other revisions. But it looks like src/jit/arm/jit_emit.h might still benefit from your patch. Could you review these patches? Thank you very much. Unfortunately, I really don't have the tuits to do much more than lurk these days. I also don't have access to a computer with the arm architecture, so I don't know if there's much more I can do as far as the patch is concerned (it'd be nice to test it to see if it worked for instance). I wish I could be of more help :-/ Paul
[perl #37287] [TODO] pdb - don't die on exceptions
Friends, Doing cage cleaning today, I noticed that there has been no activity in this thread since last August. Are the issues that were under discussion still live? Should we still be considering the various patches? Update sought. Thank you very much. kid51
[perl #44471] [PATCH] :vtable is ignored when :anon
Allison, Can you give us an update on the status of this ticket? Thank you very much. kid51
[perl #47247] [PATCH] Move executable code out of gcc_pcc header
On Thu Nov 08 08:25:28 2007, ptc wrote: James, Thanks for the report! I forgot to add parrot.h to the list of includes. Could you add: #include parrot/parrot.h just before the other include statement in gcc_pcc.c and see if things make (after realclean) nicely for you? Paul, I guess I had difficulty editing and applying this patch. Hence, my non-response for several months. Would it be possible for you to post a clean version of the patch? I will then try it out on Darwin? (But I'll ask others to try it as well, as we've been getting 10.4 vs 10.5 problems and ppc vs intel problems.) kid51
[perl #51790] Segfaults for GDBMHash in -C and -S runcores
# New Ticket Created by Bernhard Schmalhofer # Please include the string: [perl #51790] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=51790 Hi, running 'make fulltest' under Linux leaves me with segfaults for gdbmhast.t. t/dynpmc/foo.ok t/dynpmc/gdbmhash # Failed test 'get_integer' # at t/dynpmc/gdbmhash.t line 73. # Exited with error code: 139 # Received: # Segmentation fault (core dumped) # # Expected: # An unitialized GDBMHash has size 0. # An GDBMHash for a new file has size 0. # After one assignment GDBMHash has size 1. # After two assignments GDBMHash has size 2. # After 15 assignments GDBMHash has size 15. # # Failed test 'get_bool' # at t/dynpmc/gdbmhash.t line 125. # Exited with error code: 139 # Received: # Segmentation fault (core dumped) # # Expected: # An uninitialized GDBMHash is not. # An GDBMHash for a new file is not. # After one insert the GDBMHash is. # # Looks like you failed 2 tests of 13. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/13 subtests t/dynpmc/rationalok This happens only for the computed-goto and for the switched runcore. [EMAIL PROTECTED]:~/devel/Parrot/trunk$ uname -a Linux heist 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux Regards, Bernhard
[perl #38262] [CAGE] get external Perl5 modules out of the parrot repo
On So. 09. Mär. 2008, 19:11:53, [EMAIL PROTECTED] wrote: Well, it looks like we've survived for a week without Test::Builder or any other Perl 5 core module in the Parrot distribution. (Thanks to Matt Kraai for helping out with t/perl/Parrot_Test.t.) So I think we can close this ticket. kid51 I'm reopening this ticket, as there are still external Perl 5 modules in lib/Digest, lib/File, lib/IO, lib/Pod. The Perl::Critic policies in lib/Perl/Critic/Policy seem to be Parrot-specific. -- /* [EMAIL PROTECTED] */
Re: [perl #17490] Magic is useless unless verifiable.
James Keenan via RT wrote: Jonathan: You took this RT some time back. Could you give us an update on its status? (It's the oldest outstanding RT.) Resolved; PDD13 specified doing it a Different Way and that bit of PDD13 is one of the bits I've gotten around to implementing too, so this is fixed in both spec and implementation. Thanks, Jonathan
Re: [perl #40830] [PATCH] Man-Chicken's awesome hackathon throw-away patches...
2008/3/16, James Keenan via RT [EMAIL PROTECTED]: While I think the patches proposed in this ticket are moribund, the fact is that what little feedback we get on Cygwin indicates that many core tests are failing during smoke testing. See, e.g., http://smoke.parrotcode.org/smoke/parrot-smoke-0.5.3-devel-r26408-unknown--i386-cygwin-ccache-default--1205664735-3891--6759-6386-373-239-537-0--2d443430202d2d67632d6465627567202d2d72756e2d65786563--9ee766b1915c8ba87fa9a4685e9be46b.html In his patch I see a lot of useful but very old API declarations, but already included. The failing threads in t/stm/runtime.t seems to be incorrect. http://smoke.parrotcode.org/smoke/parrot-smoke-0.5.3-devel-r26408-unknown--i386-cygwin-ccache-default--1205659543-1306--11163-11120-43-260-558-7--2d443430202d2d67632d6465627567--2bdf65f4addb9388bd19ea346471b9ba.html has 100% ok on this test, and on my machine also. I would just reject it. The debug printf patch is stupid. GDB works fine on cygwin for everyone else. -- Reini Urban current perl on cygwin maintainer
[perl #47289] [PATCH] Move executable code out of jit/i386/exec_dep.h
Joshua, Paul: Can you give us an update on the status of patch still? Thank you very much. kid51
[perl #46927] [PATCH] Remove integer - pointer comparison in slice.pmc
Per response from Paul Cochrane, resolving ticket.
[perl #43414] [PATCH] jit_emit.h changes for various platforms
On Sun Mar 16 10:04:50 2008, ptc wrote: Unfortunately, I really don't have the tuits to do much more than lurk these days. I also don't have access to a computer with the arm architecture, so I don't know if there's much more I can do as far as the patch is concerned (it'd be nice to test it to see if it worked for instance). I wish I could be of more help :-/ Paul Okay, then I will rule that we won't apply the patch to src/jit/ppc/jit_emit.h, but we'll leave the other patches open for review. Thanks for the rapid response! kid51
[perl #39988] [DOCS] Stackless vtable calls to Parrot functions
On Sun Mar 16 10:02:32 2008, rgrjr wrote: I think it ought to happen, though I think Allison just wanted a ticket for updating existing PDDs, and not for a whole new PDD. I asked Allison for a clarification on 11-Mar in Will's [oops; continuation 0xb6926320 of type 22 is trying to jump from runloop 15008 to runloop 1] thread, and had been waiting for that. But I do agree that it ought to be a separate ticket. The underlying issue is still with us, but has outgrown the original ticket. Okay. I will now close this ticket. For more granular tracking, I recommend that a separate RT be opened for each existing PDD which needs updating. Thank you very much. kid51
[perl #41511] Parrot_call_sub* Incompatible with Multisubs
On Sat Feb 17 13:49:37 2007, [EMAIL PROTECTED] wrote: On Thursday 15 February 2007 08:24, Matt Diephouse wrote: If you wanted to send me some sample code that invoked both a normal sub and a MultiSub, I'd certainly take a look. I'm pretty sure the whole idea of invoke-able objects was never really thought out -- some of the logic in Sub.invoke() should be elsewhere. Committed as a TODO test in t/src/extend.t in r17034. Matt, chromatic: This test is still in TODO status as of r26404. Can you provide us with an update as to the ticket's status? Thank you very much. kid51
[perl #49532] [PATCH] test for multiple Parrot_new/Parrot_exit cycles
Added test is continuing to pass. Resolving ticket.
[perl #51794] Test in languages/urm try to call _export_to_level
# New Ticket Created by Bernhard Schmalhofer # Please include the string: [perl #51794] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=51794 Running 'make test' in 'languages/urm' gives me complaints about _export_to_level. It looks like URM::Test tries to call an internal function of Test::More. [EMAIL PROTECTED]:~/devel/Parrot/trunk/languages/urm$ make test /usr/bin/perl -c urmc urmc syntax OK cd .. /usr/bin/perl -I../lib urm/t/harness urm/t/in_out..Can't locate object method _export_to_level via package URM::Test at /home/bernhard/devel/Parrot/trunk/languages/urm/t/../lib/URM/Test.pm line 24. BEGIN failed--compilation aborted at urm/t/in_out.t line 6. # Looks like your test died before it could output anything. urm/t/in_out.. Dubious, test returned 255 (wstat 65280, 0xff00) Failed 3/3 subtests Maybe the urm tests can be tricked into using Parrot::Test::Harness. This is all with Test::More 0.75. Regards, Bernhard
Re: [perl #46223] [PATCH] Remove dead code in src/pmc/pair.pmc (Coverity CID 5)
On 16/03/2008, James Keenan via RT [EMAIL PROTECTED] wrote: Paul, I see that you touched src/pmc/pair.pmc after your last post in this thread. r22490 | paultcochrane | 2007-10-25 16:10:19 -0400 (Thu, 25 Oct 2007) | 2 lines [pmc] Removing dead code which was picked up in Coverity CID 5 Given that, should we still be considering this patch? If not, can we close the ticket? Given the contents of the commit log message, I'd say we can close this ticket. Paul
[perl #40830] [PATCH] Man-Chicken's awesome hackathon throw-away patches...
Thanks for the update. I think I'll leave this ticket open for a few more days in the hope that Matt and Steve comment.
[perl #17490] Magic is useless unless verifiable.
On Sun Mar 16 10:34:00 2008, [EMAIL PROTECTED] wrote: Resolved; PDD13 specified doing it a Different Way and that bit of PDD13 is one of the bits I've gotten around to implementing too, so this is fixed in both spec and implementation. Resolving our oldest ticket! Thanks, Jonathan. kid51
Re: [perl #47247] [PATCH] Move executable code out of gcc_pcc header
On 16/03/2008, James Keenan via RT [EMAIL PROTECTED] wrote: On Thu Nov 08 08:25:28 2007, ptc wrote: James, Thanks for the report! I forgot to add parrot.h to the list of includes. Could you add: #include parrot/parrot.h just before the other include statement in gcc_pcc.c and see if things make (after realclean) nicely for you? Paul, I guess I had difficulty editing and applying this patch. Hence, my non-response for several months. Would it be possible for you to post a clean version of the patch? I will then try it out on Darwin? (But I'll ask others to try it as well, as we've been getting 10.4 vs 10.5 problems and ppc vs intel problems.) It would probably be optimal if you tried out the patch (with the #include parrot/parrot.h addition) as I don't have access to a ppc machine to test that the patch works. I would guess that that section of code hasn't changed much since I posted the patch so it should still apply cleanly. Paul
[perl #44845] [PATCH] C++ cleanups for Solaris CC
Cage cleaning question: Can we get an update on the status of the patch proposed in this ticket? Thank you very much. kid51
[perl #45189] [PATCH] Remove Deprecated PGE Syntax
Can any of our Win32 developers examine this? Thanks.
Re: [perl #47289] [PATCH] Move executable code out of jit/i386/exec_dep.h
On 16/03/2008, James Keenan via RT [EMAIL PROTECTED] wrote: Joshua, Paul: Can you give us an update on the status of patch still? As far as I remember, it still needs to be tested on the various runcores. Paul
Re: [perl #44363] [PATCH] -D80 + bad luck = segfault
James Keenan via RT wrote: There's been no activity in this thread since last August. Can you give us an update on the issues at hand? I haven't got the problem in a while, so I think it's disappeared. I haven't watched the list closely enough to say why, but I guess it's over. Cheers, Bram Geron
[perl #51798] [PATCH] Fix some compilation warnings
# New Ticket Created by Matt Kraai # Please include the string: [perl #51798] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=51798 Howdy, The attached patch fixes the following warnings: make[1]: Entering directory `/home/kraai/src/parrot/languages' Makefile:352: warning: overriding commands for target `dotnet.realclean' Makefile:242: warning: ignoring old commands for target `dotnet.realclean' src/hash.c: In function ‘parrot_mark_hash’: src/hash.c:334: warning: comparison between signed and unsigned src/interpreter.c: In function ‘dynop_register’: src/interpreter.c:1013: warning: assignment from incompatible pointer type src/mmd.c: In function ‘mmd_sort_candidates’: src/mmd.c:1599: warning: passing argument 2 of ‘Parrot_quicksort’ from incompatible pointer type src/exec.c: In function ‘Parrot_exec’: src/exec.c:101: warning: cast discards qualifiers from pointer target type src/io/io.c: In function ‘PIO_dup’: src/io/io.c:201: warning: return from incompatible pointer type ./src/pmc/parrotio.pmc: In function ‘Parrot_ParrotIO_clone’: ./src/pmc/parrotio.pmc:411: warning: initialization from incompatible pointer type compilers/imcc/imclexer.c:55:5: warning: __STDC_VERSION__ is not defined compilers/imcc/instructions.c: In function ‘ins_print’: compilers/imcc/instructions.c:748: warning: comparison between pointer and integer compilers/imcc/reg_alloc.c: In function ‘ig_test’: compilers/imcc/reg_alloc.c:213: warning: passing argument 4 of ‘ig_get_word’ discards qualifiers from pointer target type ./md2.pmc: In function ‘Parrot_MD2_nci_MD2_Update’: ./md2.pmc:112: warning: pointer targets in passing argument 2 of ‘MD2_Update’ differ in signedness ./md2.pmc: In function ‘Parrot_MD2_nci_MD2_Final’: ./md2.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness ./md4.pmc: In function ‘Parrot_MD4_nci_MD4_Final’: ./md4.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness ./md5.pmc: In function ‘Parrot_MD5_nci_MD5_Final’: ./md5.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness ./ripemd160.pmc: In function ‘Parrot_RIPEMD160_nci_RIPEMD160_Final’: ./ripemd160.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness ./sha.pmc: In function ‘Parrot_SHA_nci_SHA_Final’: ./sha.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness ./sha1.pmc: In function ‘Parrot_SHA1_nci_SHA1_Final’: ./sha1.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness ./sha256.pmc: In function ‘Parrot_SHA256_nci_SHA256_Final’: ./sha256.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness ./sha512.pmc: In function ‘Parrot_SHA512_nci_SHA512_Final’: ./sha512.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness There are 30 warnings remaining, but I'm not sure how to fix them. The patch contains changes to imclexer.c, which was regenerated using the Debian version of flex, so you may want to regenerate it using the standard version before committing. -- Matt diff --git a/compilers/imcc/imc.h b/compilers/imcc/imc.h index d69c05e..5baf3ae 100644 --- a/compilers/imcc/imc.h +++ b/compilers/imcc/imc.h @@ -108,7 +108,7 @@ void graph_coloring_reg_alloc(PARROT_INTERP, ARGMOD(IMC_Unit *unit)) __attribute__nonnull__(2) FUNC_MODIFIES(*unit); -int ig_test(int i, int j, int N, ARGIN(const unsigned int *graph)) +int ig_test(int i, int j, int N, ARGIN(unsigned int *graph)) __attribute__nonnull__(4); void imc_reg_alloc(PARROT_INTERP, ARGIN_NULLOK(IMC_Unit *unit)) diff --git a/compilers/imcc/imcc.l b/compilers/imcc/imcc.l index ae6067e..61d54b5 100644 --- a/compilers/imcc/imcc.l +++ b/compilers/imcc/imcc.l @@ -13,8 +13,8 @@ /* HEADERIZER HFILE: none */ /* HEADERIZER STOP */ -#ifndef __STDC_VERSION_ -# define __STDC_VERSION_ +#ifndef __STDC_VERSION__ +# define __STDC_VERSION__ 0 #endif } diff --git a/compilers/imcc/imclexer.c b/compilers/imcc/imclexer.c index 7fc08b9..8297c51 100644 --- a/compilers/imcc/imclexer.c +++ b/compilers/imcc/imclexer.c @@ -14,8 +14,8 @@ /* HEADERIZER HFILE: none */ /* HEADERIZER STOP */ -#ifndef __STDC_VERSION_ -# define __STDC_VERSION_ +#ifndef __STDC_VERSION__ +# define __STDC_VERSION__ 0 #endif @@ -30,7 +30,7 @@ #define FLEX_SCANNER #define YY_FLEX_MAJOR_VERSION 2 #define YY_FLEX_MINOR_VERSION 5 -#define YY_FLEX_SUBMINOR_VERSION 33 +#define YY_FLEX_SUBMINOR_VERSION 34 #if YY_FLEX_SUBMINOR_VERSION 0 #define FLEX_BETA #endif @@ -52,7 +52,7 @@ /* C99 systems have inttypes.h. Non-C99 systems may or may not. */ -#if __STDC_VERSION__ = 199901L +#if defined (__STDC_VERSION__) __STDC_VERSION__
[perl #51796] [PATCH] Add a prototype for pobj_flag_dump
# New Ticket Created by Matt Kraai # Please include the string: [perl #51796] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=51796 Howdy, When I run make headerizer, it adds a prototype for pobj_flag_dump to src/packdump.c. The attached patch contains this change. -- Matt diff --git a/src/packdump.c b/src/packdump.c index d692d0d..477678c 100644 --- a/src/packdump.c +++ b/src/packdump.c @@ -34,6 +34,10 @@ static void PackFile_Constant_dump(PARROT_INTERP, __attribute__nonnull__(2) __attribute__nonnull__(3); +static void pobj_flag_dump(PARROT_INTERP, ARGIN(long flags)) +__attribute__nonnull__(1) +__attribute__nonnull__(2); + /* HEADERIZER END: static */
[perl #41511] Parrot_call_sub* Incompatible with Multisubs
On Sun Mar 16 10:57:07 2008, [EMAIL PROTECTED] wrote: Matt, chromatic: This test is still in TODO status as of r26404. Can you provide us with an update as to the ticket's status? Thank you very much. kid51 Sure. I investigated the issue a while back, and the whole thing is basically stalled. The code surrounding the issue (the packfile code) is a bit of a mess, which made finding a real fix difficult. I started to work on refactoring that code in order to find a fix here, but it's large, hairy, and difficult to work with. This bug should either remain open or be changed to stalled. To recap, I think this bug will require a substantial refactoring and cleanup of the packfile code. For now, I believe it's a non-trivial bug (except, perhaps, for someone with a more thorough understanding of the packfile code). My involvement with Parrot has been minimal as of late, but I'm willing to retain ownership of the ticket and fix the issue if packfile code gets cleaned up. -- Matt Diephouse
Re: [perl #50616] [PATCH] add lists to pynie
I've updated the patch to also add tuples to pynie. Arcady pynie-list-tuple.patch Description: Binary data On Feb 7, 2008, at 4:37 AM, Arcady Goldmints-Orlov (via RT) wrote: # New Ticket Created by Arcady Goldmints-Orlov # Please include the string: [perl #50616] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=50616 This patch enables pynie to parse and construct lists. Arcady pynie-list.patch
Re: [perl #41165] [PATCH] appropriate handle CRLE in Here Docs
On Sun, Mar 16, 2008 at 8:09 AM, James Keenan via RT [EMAIL PROTECTED] wrote: There's been no activity in this RT for more than a year, so I am resolving the ticket. we have a category for this called 'stalled'. it's a better reflection of status than 'closed' in cases like this in my opinion. ~jerry
Re: [perl #39823] [CAGE] tools/dev/run_indent.pl -- this should be a test
On Sun, Mar 16, 2008 at 11:05 AM, James Keenan via RT [EMAIL PROTECTED] wrote: No one has spoken up in defense of tools/dev/run_indent.pl. If no one does so within 24 hours, I will yank it from the distribution and close this ticket. +1, please do. kid51 -- Will Coke Coleda
[perl #46223] [PATCH] Remove dead code in src/pmc/pair.pmc (Coverity CID 5)
Resolved per discussion with ptc.
Re: [perl #41511] Parrot_call_sub* Incompatible with Multisubs
On Sunday 16 March 2008 12:16:06 Matt Diephouse via RT wrote: Sure. I investigated the issue a while back, and the whole thing is basically stalled. The code surrounding the issue (the packfile code) is a bit of a mess, which made finding a real fix difficult. I started to work on refactoring that code in order to find a fix here, but it's large, hairy, and difficult to work with. This bug should either remain open or be changed to stalled. To recap, I think this bug will require a substantial refactoring and cleanup of the packfile code. For now, I believe it's a non-trivial bug (except, perhaps, for someone with a more thorough understanding of the packfile code). Agreed. My involvement with Parrot has been minimal as of late, but I'm willing to retain ownership of the ticket and fix the issue if packfile code gets cleaned up. I believe Jonathan was looking into this. In particular, adding arity to Subs was the first step. -- c
[perl #39988] [DOCS] Stackless vtable calls to Parrot functions
From: James Keenan via RT [EMAIL PROTECTED] Date: Sun, 16 Mar 2008 10:46:15 -0700 On Sun Mar 16 10:02:32 2008, rgrjr wrote: I think it ought to happen, though I think Allison just wanted a ticket for updating existing PDDs, and not for a whole new PDD. I asked Allison for a clarification on 11-Mar in Will's [oops; continuation 0xb6926320 of type 22 is trying to jump from runloop 15008 to runloop 1] thread, and had been waiting for that. But I do agree that it ought to be a separate ticket. The underlying issue is still with us, but has outgrown the original ticket. Okay. I will now close this ticket. Fine by me. For more granular tracking, I recommend that a separate RT be opened for each existing PDD which needs updating. Thank you very much. kid51 I am not sure that separate tickets makes sense for what ought to be a single coordinated change. But I will submit the first ticket so you can look at it (though probably not for a while yet), and we can take it from there. -- Bob
Re: [perl #41511] Parrot_call_sub* Incompatible with Multisubs
chromatic wrote: To recap, I think this bug will require a substantial refactoring and cleanup of the packfile code. For now, I believe it's a non-trivial bug (except, perhaps, for someone with a more thorough understanding of the packfile code). Agreed. Same here. I believe Jonathan was looking into this. In particular, adding arity to Subs was the first step. Also, I already added inspect, which provides a way to get a bit more than the arity, including the numbers of different types of parameters. I can extend that further as needed. On the more general packfile code re-factoring, yes, I still plan to do it. I was somewhat distracted from Parrot guts by Rakudo during Feb, when I was trying to help get it more featureful for when I was presenting it at a couple of conferences, and so far this month have been busy doing $DAYJOB to pay the bills. Things should ease up a bit soon. Thanks, Jonathan
Re: [perl #47978] [C99] [IMCC] double free
On Saturday 23 February 2008 14:23:19 Klaas-Jan Stol wrote: On Sat, Feb 23, 2008 at 5:00 PM, Ron Blaschke [EMAIL PROTECTED] wrote: The issue seems to be caused by languages/c99/src/preamble, where: .local $iter_loop: Consider this test program. $cat m.pir .macro test .local $iter_loop: .endm $ parrot -o m.pbc --output-pbc m.pir compilers/imcc/imcc.l:992: failed assertion 'valp-s' (Remove the colon and it parses again.) that makes sense, now i see this: .local is not valid anymore to declare labels, you should use .label. Can we somehow make this an error in IMCC? I poked at the LOCAL and LABEL rules slightly, but didn't figure it out. -- c
Re: [perl #51798] [PATCH] Fix some compilation warnings
On Sunday 16 March 2008 09:19:47 Matt Kraai wrote: The attached patch fixes the following warnings: make[1]: Entering directory `/home/kraai/src/parrot/languages' Makefile:352: warning: overriding commands for target `dotnet.realclean' Makefile:242: warning: ignoring old commands for target `dotnet.realclean' src/hash.c: In function ‘parrot_mark_hash’: src/hash.c:334: warning: comparison between signed and unsigned src/interpreter.c: In function ‘dynop_register’: src/interpreter.c:1013: warning: assignment from incompatible pointer type src/mmd.c: In function ‘mmd_sort_candidates’: src/mmd.c:1599: warning: passing argument 2 of ‘Parrot_quicksort’ from incompatible pointer type src/exec.c: In function ‘Parrot_exec’: src/exec.c:101: warning: cast discards qualifiers from pointer target type src/io/io.c: In function ‘PIO_dup’: src/io/io.c:201: warning: return from incompatible pointer type ./src/pmc/parrotio.pmc: In function ‘Parrot_ParrotIO_clone’: ./src/pmc/parrotio.pmc:411: warning: initialization from incompatible pointer type compilers/imcc/imclexer.c:55:5: warning: __STDC_VERSION__ is not defined compilers/imcc/instructions.c: In function ‘ins_print’: compilers/imcc/instructions.c:748: warning: comparison between pointer and integer compilers/imcc/reg_alloc.c: In function ‘ig_test’: compilers/imcc/reg_alloc.c:213: warning: passing argument 4 of ‘ig_get_word’ discards qualifiers from pointer target type ./md2.pmc: In function ‘Parrot_MD2_nci_MD2_Update’: ./md2.pmc:112: warning: pointer targets in passing argument 2 of ‘MD2_Update’ differ in signedness ./md2.pmc: In function ‘Parrot_MD2_nci_MD2_Final’: ./md2.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness ./md4.pmc: In function ‘Parrot_MD4_nci_MD4_Final’: ./md4.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness ./md5.pmc: In function ‘Parrot_MD5_nci_MD5_Final’: ./md5.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness ./ripemd160.pmc: In function ‘Parrot_RIPEMD160_nci_RIPEMD160_Final’: ./ripemd160.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness ./sha.pmc: In function ‘Parrot_SHA_nci_SHA_Final’: ./sha.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness ./sha1.pmc: In function ‘Parrot_SHA1_nci_SHA1_Final’: ./sha1.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness ./sha256.pmc: In function ‘Parrot_SHA256_nci_SHA256_Final’: ./sha256.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness ./sha512.pmc: In function ‘Parrot_SHA512_nci_SHA512_Final’: ./sha512.pmc:127: warning: pointer targets in passing argument 2 of ‘string_from_cstring’ differ in signedness There are 30 warnings remaining, but I'm not sure how to fix them. The patch contains changes to imclexer.c, which was regenerated using the Debian version of flex, so you may want to regenerate it using the standard version before committing. Thanks, applied as r26426. Nice work in the IMCC ones; they eluded me. -- c
Re: [perl #51796] [PATCH] Add a prototype for pobj_flag_dump
On Sunday 16 March 2008 08:28:59 Matt Kraai wrote: When I run make headerizer, it adds a prototype for pobj_flag_dump to src/packdump.c. The attached patch contains this change. Thanks, applied as r26428. -- c
Re: [perl #50880] AutoReply: [PATCH] unreachable code warning in exceptions.c
On Thursday 14 February 2008 21:11:36 Andrew Whitworth wrote: Forgot the patch in the last email. Thanks, applied as r26429. -- c
Re: pdd17pmc branch review
On Monday 10 March 2008 07:24:44 François Perrad wrote: chromatic wrote: I fixed all of the compilation errors I could find as of r26285. 280 tests fail on the trunk for me and 308 fail on the branch, but they don't look like compilation errors or PDD 17 porting errors. I think the problem is in the wmlsbytecode.pmc (a singleton PMC with only one method 'load'), because the following command has no output : parrot wmlsd.pir t/examples_1.wmlsc The script wmlsd.pir is a disassembler that loads a WMLScript bytecode and dumps it. Other scripts make more complicated thinks after loading the WMLScript bytecode, but all scripts start with this loading step. Could you send me an output of the failure on the trunk on your platform ? Here you are! -- c # Failed test '! false' # at WMLScript/t/boolean.t line 25. # got: 'Method 'translate' not found for non-object # ' # expected: 'true # 3 # ' # Failed test '~ false' # at WMLScript/t/boolean.t line 37. # got: 'Method 'translate' not found for non-object # ' # expected: '-1 # 0 # ' # Failed test '- true' # at WMLScript/t/boolean.t line 49. # got: 'Method 'translate' not found for non-object # ' # expected: '-1 # 0 # ' # Failed test '++' # at WMLScript/t/boolean.t line 61. # got: 'Method 'translate' not found for non-object # ' # expected: '2 # 0 # ' # Failed test '--' # at WMLScript/t/boolean.t line 74. # got: 'Method 'translate' not found for non-object # ' # expected: '-1 # 0 # ' # Failed test 'true 2' # at WMLScript/t/boolean.t line 87. # got: 'Method 'translate' not found for non-object # ' # expected: '4 # 0 # ' # Failed test 'true true' # at WMLScript/t/boolean.t line 99. # got: 'Method 'translate' not found for non-object # ' # expected: '2 # 0 # ' # Failed test 'true 1' # at WMLScript/t/boolean.t line 111. # got: 'Method 'translate' not found for non-object # ' # expected: '0 # 0 # ' # Failed test 'true text' # at WMLScript/t/boolean.t line 123. # got: 'Method 'translate' not found for non-object # ' # expected: '4 # ' # Failed test 'true 2' # at WMLScript/t/boolean.t line 133. # got: 'Method 'translate' not found for non-object # ' # expected: '0 # 0 # ' # Failed test 'true 2' # at WMLScript/t/boolean.t line 145. # got: 'Method 'translate' not found for non-object # ' # expected: '0 # 0 # ' # Failed test 'true 1' # at WMLScript/t/boolean.t line 157. # got: 'Method 'translate' not found for non-object # ' # expected: '1 # 0 # ' # Failed test 'true 2.0' # at WMLScript/t/boolean.t line 169. # got: 'Method 'translate' not found for non-object # ' # expected: '4 # ' # Failed test 'true ^ 2' # at WMLScript/t/boolean.t line 179. # got: 'Method 'translate' not found for non-object # ' # expected: '3 # 0 # ' # Failed test 'true ^ invalid' # at WMLScript/t/boolean.t line 191. # got: 'Method 'translate' not found for non-object # ' # expected: '4 # ' # Failed test 'true | 6' # at WMLScript/t/boolean.t line 201. # got: 'Method 'translate' not found for non-object # ' # expected: '7 # 0 # ' # Failed test 'true div 2' # at WMLScript/t/boolean.t line 213. # got: 'Method 'translate' not found for non-object # ' # expected: '0 # 0 # ' # Failed test 'true div 0' # at WMLScript/t/boolean.t line 225. # got: 'Method 'translate' not found for non-object # ' # expected: '4 # ' # Failed test 'true % 2' # at WMLScript/t/boolean.t line 235. # got: 'Method 'translate' not found for non-object # ' # expected: '1 # 0 # ' # Failed test 'true div 0' # at WMLScript/t/boolean.t line 247. # got: 'Method 'translate' not found for non-object # ' # expected: '4 # ' # Failed test 'true * 3' # at WMLScript/t/boolean.t line 257. # got: 'Method 'translate' not found for non-object # ' # expected: '3 # 0 # ' # Failed test 'true * 3.14' # at WMLScript/t/boolean.t line 269. # got: 'Method 'translate' not found for non-object # ' # expected: '3.14 # 1 # ' # Failed test 'true * text' # at WMLScript/t/boolean.t line 281. # got: 'Method 'translate' not found for non-object # ' # expected: '4 # ' # Failed test 'true / 2' # at WMLScript/t/boolean.t line 291. # got: 'Method 'translate' not found for non-object # ' # expected: '0.5 # 1 # ' # Failed test 'true / 2.0' # at WMLScript/t/boolean.t line 303. # got: 'Method 'translate' not found for non-object # ' # expected: '0.5 # 1 # ' # Failed test 'true - 3' # at WMLScript/t/boolean.t line 315. # got: 'Method 'translate' not found for non-object # ' # expected: '-2 # 0 # ' # Failed test 'true - 1.5' # at WMLScript/t/boolean.t line 327. # got: 'Method
[perl #45695] [PATCH] Remove seemingly unnecessary Parrot_cont-from_ctx
Contributors to this thread: Can you give us an update on the issues that were being discussed? (There's been no activity in thread for 6 months.) Thank you very much. kid51
[perl #46593] [PATCH] better documentation on parameter passing
Can someone more familiar than I am with C header files take a look at this patch? Thank you very much.
