# New Ticket Created by "Lee Duhem"
# Please include the string: [perl #41269]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41269 >
Attached patch fix some failed tests in F
when run C:
t/compiler
# New Ticket Created by "Lee Duhem"
# Please include the string: [perl #41268]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41268 >
When C, I get these error:
src/pdb.c: In function `main':
src/pdb.c:1
On Sun, Jan 07, 2007 at 12:51:46PM +, Nicholas Clark wrote:
>
> I'm not convinced that allowing slop in expected output is a good idea.
Sometime allow some slop is convenient, like the situation in
t/examples/past.t
> It introduces (more) complexity into the tests, which increases the chance
I think we need some diff-like facility for string in Test::More
(or somewhere else appropriate), these options of diff for files
will be wanted:
-E --ignore-tab-expansion Ignore changes due to tab expansion.
-b --ignore-space-change Ignore changes in the amount of white space.
-w --ignore
# New Ticket Created by "Lee Duhem"
# Please include the string: [perl #41187]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41187 >
After update to 16418, test t/examples/past.t failed:
$ /usr/local/bin/p
On Thu, Jan 04, 2007 at 10:37:51PM +, Jonathan Worthington wrote:
> Lee Duhem (via RT) wrote:
> >This patch suppress some uninitialized value warning in
> >config/inter/yacc.pm when use --maintainer option at configure.
> >
> I'm kinda concerned about what wil
# New Ticket Created by "Lee Duhem"
# Please include the string: [perl #41165]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41165 >
Current parrot(in fact, lexical analyzer of PIR) don't play well
with
On Tue, Jan 02, 2007 at 06:52:14AM -0800, jerry gay wrote:
> these tests pass on windows, so i didn't catch it when i added this
> file. it seems there's something funny with parrot heredocs and CRLF.
> i don't know if this is expected behavior or not (it's untested.) i'll
> have to look further.
# New Ticket Created by "Lee Duhem"
# Please include the string: [perl #41163]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41163 >
This patch suppress some uninitialized value warning in config/inter/yac
# New Ticket Created by "Lee Duhem"
# Please include the string: [perl #41158]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41158 >
The here docs in test C cause t/op/cmp-nonbranch.t abnormal exit,
for exam
# New Ticket Created by "Lee Duhem"
# Please include the string: [perl #41157]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41157 >
The attached patch fix a typo in t/op/cmp-nonbranch.t and append
# New Ticket Created by "Lee Duhem"
# Please include the string: [perl #41159]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41159 >
2007/1/1, Debian User <[EMAIL PROTECTED]>:
> This patch fix th
2007/1/1, Debian User <[EMAIL PROTECTED]>:
This patch fix the wrong parrot include path, for example:
before patch:
/home/lee/parrot/workinginclude
after patch:
/home/lee/parrot/working/include
You can get the patch from
http://groups.google.com/group/perl.perl6.compiler/browse_thread/thread/
# New Ticket Created by "Lee Duhem"
# Please include the string: [perl #41154]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41154 >
This patch makes code struct and output of examples/pasm/stack.pasm
mo
# New Ticket Created by "Lee Duhem"
# Please include the string: [perl #41139]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41139 >
The attached patch of the first message have some no-ASCII characters,
t
# New Ticket Created by "Lee Duhem"
# Please include the string: [perl #41140]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41140 >
Sorry, forget the patch...
Index: s
Sorry, forget the patch...
Index: src/packfile.c
===
--- src/packfile.c (revision 16268)
+++ src/packfile.c (working copy)
@@ -2187,7 +2187,7 @@
default_dump_header(interp, self);
-PIO_printf(interp, "mappings => [\n");
+
The attached patch of the first message have some no-ASCII characters,
this patch fix that. Otherwise, there are same.
This patch makes pdump's output about debug segment more consistent:
before patch:
BYTECODE_/tmp/t.pir_DB => [ # offs ..., size 33, ... mappings => [
after patch:
BYTECODE_/tmp/t.pir_DB => [ # offs ..., size 33, ...
mappings => [
$ diffstat /tmp/packfile.patch
packfile.c |4 ++--
1 files
All it does is turn on cperl mode for emacs, and set tabs to 4 spaces
for vim and emacs. Not likely to significantly interfere with any
repository you work on. (I actually gave up on the tab key in vim years
ago. I type literal spaces, and my brain automatically adjusts my
indenting to the surroun
My vote is on removing all emacs and vim settings from our source code
files.
and so you can get really bad code appearance.
looks like get the major OS version number is enough.
2006/12/8, via RT James Keenan <[EMAIL PROTECTED]>:
# New Ticket Created by James Keenan
# Please include the string: [perl #41055]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display
+The ultimate goal of Parrot is portability to more-or-less the same
+platforms as Perl 5, including AIX, BeOS, BSD/OS, Cygwin, Darwin,
+Debian, DG/UX, Domain/OS, DragonFlyBSD, DYNIX/ptx, Embedix, EPOC,
+FreeBSD, Gentoo, HP-UX, IRIX, Linux, Mac OS (Classic), Mac OS X,
+Mandriva, Minix, MS-DOS, Net
We have too many bugs. We could use more programmers and testers and
documenters.
and some examples need to update, for example, replace deprecated syntax with
new, etc. For newcomer, examples is good start point to learn, but
only if it's up to date.
24 matches
Mail list logo