Parrot Bug Summary
Parrot Bug Summary http://rt.perl.org/rt3/NoAuth/parrot/Overview.html Generated at Mon Sep 10 13:00:03 2007 GMT --- * Numbers * New Issues * Overview of Open Issues * Ticket Status By Version * Requestors with most open tickets --- Numbers Ticket Counts: 17 new + 559 open = 576 Created this week: 18 Closed this week: 30 --- New Issues New issues that have not been responded to yet 1 - 2 weeks old 45055 [TODO] JIT segs are currently not built 45023 SUGGESTION inlining subs 2 - 3 weeks old 44979 [BUG] TGE reports an error, but won't say which line it's on. 44945 [CAGE] Add Documentation to Undef PMC 44875 YA Tcl segfault 44861 [TODO]: remove compiler warnings note from README 44851 Update step 2.f in release_manager_guide.pod 3 - 4 weeks old 44765 [PATCH] Don't reuse interpreter argument on stack 4 - 5 weeks old 44487 Exporter docs rely on t/pmc/exporter.t for examples 44471 [PATCH] :vtable is ignored when :anon 5 - 6 weeks old 44307 PIR tutorial 6 - 7 weeks old 44139 opcodes, warnings, and exceptions 7 - 8 weeks old 8 - 9 weeks old 9 - 10 weeks old 10 - 11 weeks old 11 - 12 weeks old 12 - 13 weeks old 13 - 14 weeks old 14 - 15 weeks old 15 - 16 weeks old 16 - 17 weeks old 17 - 18 weeks old 18 - 19 weeks old 19 - 20 weeks old 20 - 21 weeks old --- Overview of Open Issues PlatformSeverity Tag Lang aix0abandoned 0 5005threads 0 Amber0 All2fatal 3 bounce0 BASIC0 bsdos 0High 1 Bug 61 bc 0 cygwin 7low 0 compiler 1 befunge 0 cygwin_nt 0medium0 configure 0 bf 0 darwin 5none 0 core 0 cola 0 dec_osf0Normal1 dailybuild0 forth0 dgux 0unknown 0 docs 2 jako 0 dos0Wishlist 3 duplicate 0 Lisp 2 dynixptx 0 install 1 m4 0 freebsd8 library 0 ook 0 generic0 notabug 0 perl61 gnu0 notok 0 plot 0 HPUX 2 ok0 punie0 irix 0 Patch42 pynie2 irix64 0 regex 0 python 0 Linux 3 sendToCPAN0 ruby 0 lynxos 0 Todo289 scheme 0 mac0 unknown 0 tcl 72 machten0 utilities 0 urm 0 macos 0 wontfix 0 Zcode0 MacOS X2 mswin320 netbsd 1 next 0 openbsd2 os20 os390 0 other 0 powerux0 qnx0 riscos 0 sco0 Solaris5 sunos 1 svr4 0 svr5 0 sysv 0 unicos 0 unicosmk 0 unix 0 unknown0 uts0 vms0 VOS0 Win32 10 --- Ticket Status By Version New or OpenResolved --- Requestors with most open tickets Paul Cochrane 147 James Keenan 56 Will Coleda 44 Jerry Gay38 chromatic26 jerry gay25 Matt Diephouse 22 Chip Salzenberg 15 Andy Lester 15 Patrick R. Michaud 14 --- * Total Issues * New Issues * Overview of Open Issues * Ticket Status By Version * Requestors with most open tickets --- This page is CPU intensive to create, it will be updated only once every 30 minutes
Re: [perl #42769] can't create a variable named 'object'
On Sun, Sep 09, 2007 at 04:18:04AM -0700, Bernhard Schmalhofer via RT wrote: On Fri Apr 27 09:36:50 2007, particle wrote: it seems that 'object' is a reserved word in imcc, it's a synonym for 'pmc'. it seems undocumented, and i don't see a reason for it--we already have a word for 'pmc'. I removed 'object' from IMCC lexer and grammar, so it's not a reserved word anymore and can be normally used as a variable name: The patch from smash did not apply cleanly any more, so I manually applied it and add a test. The new patch is attached. Does anybody mind if 'object' is removed as an alias of 'pmc'? As 'object' hasn't been documented, I think that no deprecation cycle is necessary. I agree, let's eliminate 'object' asap. Pm
Re: [perl #42769] Names of basic PMC serve as keywords in PIR
On Sun, Sep 09, 2007 at 10:38:11AM -0700, Bernhard Schmalhofer via RT wrote: On So. 29. Apr. 2007, 06:01:16, kjs wrote: In r21167 the keyword 'object', as a synonym of 'pmc', was removed from PIR. However the question from kjs remains to be answered: related to this, I think that imcc also allows for built-in types as types. such as .local Array a etc. (sorry can't check; don't have my own pc around here, this is a public pc) (I added some notes about this and other PIR cleanups in languages/PIR and I think also in compilers/pirc IIRC). IMHO, this is not needed; pmc is sufficient, and it'd be nice to keep PIR as simple as possible, after all it's an intermediate language. Moreover, everytime a built-in type is added (although not happening that often) the grammar would have to be updated to stay consistent. I second the suggestion from kjs. It isn't helpful to be able to say: .local Array my_string my_string = new String In fact, I think many PIR programmers will find this confusing. Let's stick with 'pmc' for now -- we can extend it later if need be. Pm
[perl #45013] Configure fails if prefix ends with '/'
On Sun Sep 09 21:47:48 2007, coke wrote:
My suggestion would be to modify the code that take the prefix arg to
silently drop the
trailing slash; if we're adding in the slash everywhere we need it
later, this will avoid the
users having to know the details of our makefile-gen process.
Please review patch attached. Note: as yet I haven't tested it.
kid51
Index: config/init/install.pm
===
--- config/init/install.pm (revision 21171)
+++ config/init/install.pm (working copy)
@@ -66,7 +66,9 @@
my ( $self, $conf ) = @_;
my $prefix = $conf-options-get('prefix') || /usr/local;
+$prefix =~ s{/$}{};
my $ep = $conf-options-get('exec-prefix');
+$ep =~ s{/$}{};
my $eprefix = $ep ? $ep : $prefix;
# --bindir=DIR user executables [EPREFIX/bin]
Re: [perl #45309] [PATCH] sign function
On Sun, Sep 09, 2007 at 09:19:05PM -0500, Joshua Isom wrote: On Sep 9, 2007, at 6:40 PM, Doug McNutt wrote: At 21:16 +0100 9/9/07, Nicholas Clark wrote: On Sun, Sep 09, 2007 at 10:56:20AM -0700, Jrg Plate wrote: # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=45309 This patch implements the sign function for I, N, BigInt and Complex numbers. I'm curious as to why these ops should be added. These things can easily be done with PIR, and any compiler can auto generate the code for that. Not only that, but the Ccmp op already does exactly what we want (perhaps with the exception of negative infinity or NANs -- I'd have to think about those). cmp I0, N0, 0.0 # $I0 is -1, 0, or 1 At any rate, I'd be against adding a separate set of sign opcodes, in favor of just using cmp or writing special-purpose subs to handle it. Pm
[perl #45013] Configure fails if prefix ends with '/'
Better (to make sure that $ep is defined before we try a substitution on
it):
Index: config/init/install.pm
===
--- config/init/install.pm (revision 21171)
+++ config/init/install.pm (working copy)
@@ -66,7 +66,9 @@
my ( $self, $conf ) = @_;
my $prefix = $conf-options-get('prefix') || /usr/local;
+$prefix =~ s{/$}{};
my $ep = $conf-options-get('exec-prefix');
+$ep =~ s{/$}{} if defined $ep;
my $eprefix = $ep ? $ep : $prefix;
# --bindir=DIR user executables [EPREFIX/bin]
Re: [perl #42769] Names of basic PMC serve as keywords in PIR
Patrick R. Michaud schrieb: related to this, I think that imcc also allows for built-in types as types. such as .local Array a etc. (sorry can't check; don't have my own pc around here, this is a public pc) (I added some notes about this and other PIR cleanups in languages/PIR and I think also in compilers/pirc IIRC). In fact, I think many PIR programmers will find this confusing. Let's stick with 'pmc' for now -- we can extend it later if need be. The question is not whether this feature should be added, but whether it should be first deprecated and then removed. Currently .sub main :main .local Array my_string my_string = new String my_string = 'hello' say my_string .end is valid PIR. Regards, Bernhard
Re: [perl #45013] Configure fails if prefix ends with '/'
On Monday 10 September 2007 10:41:22 James Keenan via RT wrote:
Better (to make sure that $ep is defined before we try a substitution on
it):
Index: config/init/install.pm
===
--- config/init/install.pm(revision 21171)
+++ config/init/install.pm(working copy)
@@ -66,7 +66,9 @@
my ( $self, $conf ) = @_;
my $prefix = $conf-options-get('prefix') || /usr/local;
+$prefix =~ s{/$}{};
my $ep = $conf-options-get('exec-prefix');
+$ep =~ s{/$}{} if defined $ep;
my $eprefix = $ep ? $ep : $prefix;
# --bindir=DIR user executables [EPREFIX/bin]
Is the chance that $prefix ends in slash-newline sufficiently rare that the $
anchor is better than \z?
(Yes, I *have* written code to work with Mac OS 9 filesystems; why are you
looking at me as if I'm completely paranoid?)
-- c
Re: Test::Harness 2.99_02 vs. Parrot
# from Andy Armstrong # on Monday 10 September 2007 11:13 am: On 10 Sep 2007, at 19:12, Andy Armstrong wrote: What are the steps a parrot-n00b would take to be able to reproduce your results? svn co https://svn.perl.org/parrot/trunk parrot perl Configure.pl make make test If your Test::Harness is 2.99_+, you'll see lots of places where the -I switch angers the '#!./parrot'. I tend to think this is an abuse of Test::Harness and therefore parrot should bundle Test-Harness-2.64 in their distro (at least, until they get away from it.) Sounds like Eric's got it under control :) More or less (but there's only one of me.) From prove's point of view, the parrot test suite is a wreck in terms of how it defines which tests are to be run. Some are blacklisted, activated by options, etc. This logic is also (potentially) distributed to every $(find -name harness) file in the tree. So, this is only a *start* because it currently has no way to know which test files to run. http://scratchcomputing.com/tmp/runtests --Eric -- As an old bass player friend of mine used to say: throw money, don't clap. --Tony Parisi --- http://scratchcomputing.com ---
Re: [perl #42769] Names of basic PMC serve as keywords in PIR
On Mon, Sep 10, 2007 at 07:47:58PM +0200, Bernhard Schmalhofer wrote: Patrick R. Michaud schrieb: related to this, I think that imcc also allows for built-in types as types. such as .local Array a etc. (sorry can't check; don't have my own pc around here, this is a public pc) (I added some notes about this and other PIR cleanups in languages/PIR and I think also in compilers/pirc IIRC). In fact, I think many PIR programmers will find this confusing. Let's stick with 'pmc' for now -- we can extend it later if need be. The question is not whether this feature should be added, but whether it should be first deprecated and then removed. Yes, I understand this. I'm saying that even though .local Array mystring is currently allowed, AFAIK there aren't any PIR programs that use this. Thus I'm saying we should stick with only using .local pmc ..., and deprecate/remove .local Array ... to prevent others from being confused if they ever see it in a PIR program. Pm
Parrot Hackathon in Pittsburgh
I'll be attending the Pittsburgh Perl Workshop to present and host a Parrot hackathon: http://pghpw.org October 13-14, 2007 I'll be on hand to help new contributors get started, answer questions, and work on code. October 13th also happens to be the Parrot bug squashing day for the month (Saturday before the release), so we'll work on closing tickets. If you're nearby, please join us. Allison
Re: [perl #45023] SUGGESTION inlining subs
On Tue, Aug 28, 2007 at 09:37:39AM -0700, Debbie Harry wrote: # New Ticket Created by Debbie Harry # Please include the string: [perl #45023] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=45023 Maybe it would be useful to support inlining of subs (at PIR level?) This would support good programming style. Well, I'm a bit confused as to what's being asked here, so I'll go ahead and ask for some clarification. Are you asking for the ability to define subs in PIR such that any PIR-based calls to those subs are then inlined? Or are you looking at this from more of a high-level language (HLL) perspective, such that someone writing in a HLL can designate certain blocks as being suitable for inlining? Pm
Re: [perl #45249] [BUG] r21103-21121 won't build on 64-bit intel
On Sat, Sep 08, 2007 at 12:42:23AM -0700, chromatic wrote: On Friday 07 September 2007 09:32:51 Patrick R.Michaud wrote: Chromatic is already aware of this issue, but I thought I'd file a ticket for it that others can hang information on. Starting with r21103, Parrot won't build on my 64-bit platform. Here's a patch to fix the IMCC parser, mostly by porting the decorations from the revisions I listed previously into compilers/imcc/imcc.y and regenerating everything. All tests still pass for me on 32-bit x86 Linux. Applying the patch and running Configure.pl with --maintainer causes Parrot to build and run again for me on 64-bit linux. I end up failing one test (#9) in t/pmc/fixedfloatarray.t . I vote in favor of applying the patch, since it seems to allow Parrot to build on my system again. :-) Pm
Re: [perl #45249] [BUG] r21103-21121 won't build on 64-bit intel
On Monday 10 September 2007 13:49:30 Patrick R. Michaud wrote: I vote in favor of applying the patch, since it seems to allow Parrot to build on my system again. :-) Applied in r21175. Can you file a separate bug for t/pmc/fixedfloatarray.t? I think that's a different problem. -- c
Re: Parrot Hackathon in Pittsburgh
Allison Randal wrote: I'll be attending the Pittsburgh Perl Workshop to present and host a Parrot hackathon: http://pghpw.org October 13-14, 2007 I'll be there as well, speaking on coverage analysis with Perl. Some of the other sessions look interesting, so it will be tough to choose between them and the hackathon. Nonetheless, I should at least be able to stick my head in. kid51
[perl #45013] Configure fails if prefix ends with '/'
On Mon Sep 10 10:53:43 2007, [EMAIL PROTECTED] wrote:
Is the chance that $prefix ends in slash-newline sufficiently rare
that the $
anchor is better than \z?
You mean, for the first time in 7-1/2 years of doing Perl, I'm going to
have to learn what the \z modifier does?
c: you sure know how to hurt a guy!
Please evaluate the patch attached, which renames one test file, adds
another test file, and revises config/init/install.pm.
Can we get some tests on Win32 as well? And how about that Mac OS 9?
kid51
Index: MANIFEST
===
--- MANIFEST(revision 21176)
+++ MANIFEST(working copy)
@@ -1,7 +1,7 @@
# ex: set ro:
# $Id$
#
-# generated by tools/dev/mk_manifest_and_skip.pl Mon Sep 10 22:33:35 2007 UT
+# generated by tools/dev/mk_manifest_and_skip.pl Tue Sep 11 01:21:18 2007 UT
#
# See tools/dev/install_files.pl for documentation on the
# format of this file.
@@ -2923,7 +2923,8 @@
t/configure/101-init_manifest.02.t []
t/configure/102-init_defaults.01.t []
t/configure/102-init_defaults.02.t []
-t/configure/103-init_install.t []
+t/configure/103-init_install.01.t []
+t/configure/103-init_install.02.t []
t/configure/104-init_miniparrot.t []
t/configure/105-init_hints.01.t []
t/configure/105-init_hints.02.t []
Index: t/configure/103-init_install.t
===
--- t/configure/103-init_install.t (revision 21176)
+++ t/configure/103-init_install.t (working copy)
@@ -1,107 +0,0 @@
-#! perl
-# Copyright (C) 2007, The Perl Foundation.
-# $Id$
-# 103-init_install.t
-
-use strict;
-use warnings;
-use Test::More tests = 19;
-use Carp;
-use Cwd;
-use Data::Dumper;
-use File::Temp qw(tempdir);
-use lib qw( lib t/configure/testlib );
-use Parrot::Configure;
-use Parrot::Configure::Options qw( process_options );
-use_ok('config::init::install');
-use Parrot::Configure::Test qw( test_step_thru_runstep);
-
-my $cwd = cwd();
-{
-my $tdir = tempdir();
-my $tdir1 = tempdir();
-my $args = process_options( {
-argv= [
-qq{--prefix=$tdir},
-qq{--exec-prefix=$tdir},
-qq{--bindir=$tdir1},
-qq{--sbindir=$tdir1},
-qq{--libexecdir=$tdir1},
-qq{--datadir=$tdir1},
-qq{--sysconfdir=$tdir1},
-qq{--sharedstatedir=$tdir1},
-qq{--localstatedir=$tdir1},
-qq{--libdir=$tdir1},
-qq{--includedir=$tdir1},
-qq{--oldincludedir=$tdir1},
-qq{--infodir=$tdir1},
-qq{--mandir=$tdir1},
-],
-mode= q{configure},
-} );
-
-my $conf = Parrot::Configure-new;
-test_step_thru_runstep($conf, q{init::install}, $args);
-
-is($conf-data-get('prefix'), $tdir,
---prefix option confirmed);
-is($conf-data-get('exec_prefix'), $tdir,
---exec-prefix option confirmed);
-is($conf-data-get('bindir'), $tdir1,
---bindir option confirmed);
-is($conf-data-get('sbindir'), $tdir1,
---sbindir option confirmed);
-is($conf-data-get('libexecdir'), $tdir1,
---libexecdir option confirmed);
-is($conf-data-get('datadir'), $tdir1,
---datadir option confirmed);
-is($conf-data-get('sharedstatedir'), $tdir1,
---sharedstatedir option confirmed);
-is($conf-data-get('localstatedir'), $tdir1,
---localstatedir option confirmed);
-is($conf-data-get('libdir'), $tdir1,
---libdir option confirmed);
-is($conf-data-get('includedir'), $tdir1,
---includedir option confirmed);
-is($conf-data-get('oldincludedir'), $tdir1,
---oldincludedir option confirmed);
-is($conf-data-get('infodir'), $tdir1,
---infodir option confirmed);
-is($conf-data-get('mandir'), $tdir1,
---mandir option confirmed);
-}
-
-pass(Completed all tests in $0);
-
-### DOCUMENTATION ###
-
-=head1 NAME
-
-103-init_install.t - test config::init::install
-
-=head1 SYNOPSIS
-
-% prove t/configure/103-init_install.t
-
-=head1 DESCRIPTION
-
-The files in this directory test functionality used by FConfigure.pl.
-
-The tests in this file test subroutines exported by config::init::install.
-
-=head1 AUTHOR
-
-James E Keenan
-
-=head1 SEE ALSO
-
-config::init::install, FConfigure.pl.
-
-=cut
-
-# Local Variables:
-# mode: cperl
-# cperl-indent-level: 4
-# fill-column: 100
-# End:
-# vim: expandtab
[perl #43313] [TODO] config/inter/yacc.pm: Write unit tests
Patches committed to trunk in r21177. Resolving ticket.
