not yet working
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
Dflags.patch
Description: Binary data
On Mon, Sep 21, 2009 at 8:26 AM, Will Coleda via RT
parrotbug-follo...@parrotcode.org wrote:
Sorry for the delay - this patch had stalled waiting for review due to a
ticketing system
changeover, and in the meantime, no longer applies cleanly against parrot
HEAD.
Can you rebase this patch
# New Ticket Created by v-lk
# Please include the string: [perl #69524]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=69524
Hello!
I've installed rakudo on my PC with Ubuntu AMD64.
Everything was OK, BUT later I
--
Will Coke Coleda
On Oct 1, 2009, at 10:32, v-lk (via RT) parrotbug-follo...@parrotcode.org
wrote:
# New Ticket Created by v-lk
# Please include the string: [perl #69524]
# in the subject line of all future correspondence about this issue.
# URL:
I have moved this ticket to the Trac system:
https://trac.parrot.org/parrot/ticket/850. Please continue discussion
there.
Thank you very much.
kid51
On Tue Apr 21 05:36:53 2009, bacek wrote:
On Sun Aug 24 08:06:29 2008, jk...@verizon.net wrote:
There is no more tools/dev/ops_renum.mak. Can we close this ticket?
The only reason I did not previously close it was Coke's expression of a
desire to pull this into the main Makefile. But I'll
On Thu, 16 Apr 2009, NotFound via RT wrote:
Closing this ticket, the patch is very outdated and nobody is reporting
related problems. If someone found any problem with the Solaris C++
compiler, or any other, please crate a new ticket in parrot trac.
The files may have moved so that the patch
# New Ticket Created by Andy Wardley
# Please include the string: [perl #63394]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=63394
This patch:
1) Updates the docs/pct/gettingstarted.pod documentation to reflect
# New Ticket Created by Saleem A. Ansari
# Please include the string: [perl #63036]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=63036
Fixed typos in docs/book
ch09_pct.pod |2 +-
ch11_pmcs.pod|2
# New Ticket Created by Ron Schmidt
# Please include the string: [perl #62588]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=62588
The line in the test script read: # 'inspect'() # XXX must fix
'attributes'
been superseded. Recommending patch below:
Index: src/ops/pmc.ops
===
--- src/ops/pmc.ops (revision 35872)
+++ src/ops/pmc.ops (working copy)
@@ -48,7 +48,7 @@
new P0, 'ResizableBooleanArray'
Optionally a PMC may be passed
On Mon, Jan 12, 2009 at 6:26 PM, Ovid
publiustemp-perl6langua...@yahoo.comwrote:
- Original Message
From: jason switzer jswit...@gmail.com
If we wanted language dependent version, use :leading, :trailing, and
:both.
That will require each implementation properly handle the
Ovid wrote:
Seems Larry's agreed to the .trim method. There are bits that are not agreed
upon, so this patch only implements what we've agreed upon. It relies on the
new S29-str/trim.t test in pugs. I committed that earlier and updated
t/spectest.data.
In other words, the patch
- Original Message
From: Ovid publiustemp-perl6interna...@yahoo.com
This patch implements the .trim() method for strings.
Now that I'm reading S29, I see there is no .trim() method there. I got that
because it was referenced in pugs in the cookbook (not in tests, though
On Mon, Jan 12, 2009 at 07:01:25AM -0800, Ovid wrote:
I could optionally make the following work:
$string.trim(:leading0);
$string.trim(:trailing0);
Alternatively, those could be ltrim() and rtrim().
'left' and 'right' are probably not the right names for functions which
- Original Message
From: jesse je...@fsck.com
On Mon, Jan 12, 2009 at 07:01:25AM -0800, Ovid wrote:
I could optionally make the following work:
$string.trim(:leading0);
$string.trim(:trailing0);
Alternatively, those could be ltrim() and rtrim().
'left'
On 2009-01-12 Ovid publiustemp-perl6interna...@yahoo.com wrote:
Um, er. Damn. Now I'm wondering how my leading and trailing
trimming works with Hebrew. How are the strings implemented
internally?
RTL (and bidi) languages are written in strings so that the character
order is the logical,
On Mon, Jan 12, 2009 at 05:04:50AM -0800, Ovid wrote:
: ...the trivial $string.trim and trim($string) case.
Hmm, I'd think .trim should work like .chomp, and return the trimmed
string without changing the original. You'd use $str.=trim to do it
in place.
Can't say I really like the negated
- Original Message
From: Larry Wall la...@wall.org
On Mon, Jan 12, 2009 at 05:04:50AM -0800, Ovid wrote:
: ...the trivial $string.trim and trim($string) case.
Hmm, I'd think .trim should work like .chomp, and return the trimmed
string without changing the original. You'd use
Ovid wrote:
- Original Message
In the pir, doesn't the s = self line copy self, thus ensuring that I'm changing s and not self?
No, it's binding.
Or do I need s = clone self (or however it's written).
Yeah, but also note that substr would return a copy...
Can't say I
On Mon, 2009-01-12 at 07:01 -0800, Ovid wrote:
- Original Message
I could optionally make the following work:
$string.trim(:leading0);
$string.trim(:trailing0);
Alternatively, those could be ltrim() and rtrim(). If you need to
dynamically determine what you're
On Mon, Jan 12, 2009 at 09:33:32AM -0800, Geoffrey Broadwell wrote:
: That of course raises the question of how one *would* properly override
: trim's concept of whitespace
Well, given that .trim is essentially just .comb(/\S.*\S/), which in
turn is really just m:g/(\S.*\S)/, I don't see
submitted a patch for Rakudo which implements this for the trivial
$string.trim and trim($string) case. The optional :leading and :trailing
parameters aren't there.
I'm happy to finish the work according to whatever spec is agreed upon. I want
this badly enough that it's important to me :)
Cheers
- Original Message
I could optionally make the following work:
$string.trim(:leading0);
$string.trim(:trailing0);
Alternatively, those could be ltrim() and rtrim(). If you need to dynamically
determine what you're going to trim, you'd couldn't just set variables to do
On Mon, Jan 12, 2009 at 9:01 AM, Ovid
publiustemp-perl6langua...@yahoo.comwrote:
- Original Message
I could optionally make the following work:
$string.trim(:leading0);
$string.trim(:trailing0);
Alternatively, those could be ltrim() and rtrim(). If you need to
Seems Larry's agreed to the .trim method. There are bits that are not agreed
upon, so this patch only implements what we've agreed upon. It relies on the
new S29-str/trim.t test in pugs. I committed that earlier and updated
t/spectest.data.
In other words, the patch is a tad clearer
Jonathan (), Ovid (), Larry ():
Can't say I really like the negated options though. They smell funny.
Agreed, but ltrim and rtrim will disappoint Israelis and dyslexics alike.
Suggestions welcome as I can't think of anything better.
The .Net framework calls 'em TrimStart and TrimEnd (and
- Original Message
Agreed, but ltrim and rtrim will disappoint Israelis and dyslexics alike.
Suggestions welcome as I can't think of anything better.
The .Net framework calls 'em TrimStart and TrimEnd (and has a Trim that does
both). So maybe trim_start and trim_end if we
Ovid ():
=item trim
our Str multi Str::trim ( Str $string )
Removes leading and trailing whitespace from a string.
=cut
I could optionally make the following work:
$string.trim(:leading0);
$string.trim(:trailing0);
Setting leading or trailing to false (they default to true)
On Jan 12, 2009, at 11:27 AM, Carl Mäsak wrote:
How about .trim(:start) and .trim(:end)?
And .trim(:both) for orthogonality.
--
Andy Lester = a...@petdance.com = www.petdance.com = AIM:petdance
- Original Message
From: Geoffrey Broadwell ge...@broadwell.org
When I saw your proposed syntax above, instead of reading don't trim
leading/trailing whitespace, I read change the definition of
'whitespace' to 'codepoint 0' for leading/trailing.
That of course raises the question
This is an update to my last patch (which you may not see because I sent it
from the wrong email address). Here are my updated notes:
This patch implements the .trim() method for strings.
Problem: I don't like the magic number '32
not_whitespace = is_cclass 32, s, start
But I couldn't
This patch implements the .trim() method for strings.
Two problems:
1. I don't like the double-negative, but I was unsure how to get rid of it.
unless not_whitespace goto done
2. I don't like the magic number '32
not_whitespace = is_cclass 32, s, start
$I0 = is_cclass
- Original Message
This patch implements the .trim() method for strings.
Now that I'm reading S29, I see there is no .trim() method there. I got that
because it was referenced in pugs in the cookbook (not in tests, though) and I
was trying to get the examples to run. Bummer
I was pretty averse to adding an additional configure step myself. The
problem is that warnings.pm checks specifically for supported compiler
flags and I didn't want to include other things there. The bug is that
gcc.pm is hardcoded for version 4.x rather than checking. I didn't want to
donald.hun...@gmail.com wrote:
I was pretty averse to adding an additional configure step myself. The
problem is that warnings.pm checks specifically for supported compiler
flags and I didn't want to include other things there. The bug is that
gcc.pm is hardcoded for version 4.x rather than
On Thu, Jan 8, 2009 at 15:42, Mark Glines m...@glines.org wrote:
donald.hun...@gmail.com wrote:
I was pretty averse to adding an additional configure step myself. The
problem is that warnings.pm checks specifically for supported compiler flags
and I didn't want to include other things there.
# New Ticket Created by Donald Hunter
# Please include the string: [perl #62010]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=62010
This patch fixes a problem with gcc 3.4.6 on Linux where -fvisibility=hidden
of the third chapter in the book. This patch fixes it.
--
Christian
fix_doesnt_typo.patch
Description: Binary data
# New Ticket Created by Saleem A. Ansari
# Please include the string: [perl #61874]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=61874
Fixed typos in docs/book
ch08_architecture.pod | 11 +--
# New Ticket Created by Daniel Keane
# Please include the string: [perl #61800]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=61800
Implements array_fill() function within pipp.
Files affected:
*
# New Ticket Created by Saleem A. Ansari
# Please include the string: [perl #61812]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=61812
Removed Duplicate example code for creating Foo class in
# New Ticket Created by Ovid
# Please include the string: [perl #61786]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=61786
Numerous examples of it's which should be its and various other corrections
for
# New Ticket Created by Daniel Keane
# Please include the string: [perl #61788]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=61788
Remove commented code from src/pct/actions.pm
Make a small change to
# New Ticket Created by Daniel Keane
# Please include the string: [perl #61696]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=61696
First stab at implementing array() function and '=' within pipp.
Changes made:
*
# New Ticket Created by Saleem A. Ansari
# Please include the string: [perl #61638]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=61638
Fixed typos in docs.
book/ch01_overview.pod | 10 +-
# New Ticket Created by Daniel Keane
# Please include the string: [perl #61620]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=61620
A small patch to add do-while functionality to pipp.
Files changed:
* t/php
On Thu, Dec 11, 2008 at 06:19:14AM -0800, Will Coleda via RT wrote:
On Thu Dec 11 01:51:23 2008, fperrad wrote:
The new opcode 'box' is limited by its 3 signatures that target Float,
Integer String.
I propose the 3 following new opcodes :
- true
- false
These can be approximated
I just tried to build parrot with g++ on darwin/intel to see if I could
replicate the initial failure
reported in the ticket, but am unable to. (g++ is detected as gcc, and then
we pass it an option
that makes it explode.)
What Configure options do you used? I usually do:
--cc=g++
# New Ticket Created by François PERRAD
# Please include the string: [perl #61286]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=61286
The new opcode 'box' is limited by its 3 signatures that target Float,
Integer
2008/12/11 Will Coleda via RT [EMAIL PROTECTED]:
On Thu Dec 11 01:51:23 2008, fperrad wrote:
The new opcode 'box' is limited by its 3 signatures that target Float,
Integer String.
I propose the 3 following new opcodes :
- true
- false
These can be approximated with:
$P0 = box 1
$P0
On Thu, Dec 11, 2008 at 11:10 AM, François Perrad
[EMAIL PROTECTED] wrote:
2008/12/11 Will Coleda via RT [EMAIL PROTECTED]:
On Thu Dec 11 01:51:23 2008, fperrad wrote:
The new opcode 'box' is limited by its 3 signatures that target Float,
Integer String.
I propose the 3 following new opcodes
On Thursday 11 December 2008 08:20:06 Will Coleda wrote:
As I understand it, box is designed to deal /only/ with promoting the
3 basic register types (SIN) to PMCs of the appropriate HLL type (just
like autoboxing in PCC), not to provide a way to promote literal
values for arbitrary core
to the directory rpmbuild in the home-directory of the user. So the
command:
sudo cp parrot-$(VERSION).tar.gz /usr/src/*/SOURCES
does not work under Fedora 10. This patch modifies
config/gen/makefiles/root.in to generate a Makefile that builds the
RPMs in the subdirectory rpmbuild
it only does Read-Eval-Loop.
This patch adds a simple Print step and a new attribute
commandline_result_prompt similar to commandline_prompt, defaulting to
= .
It also changes the default commandline_prompt toto make the
two vertically aligned.
A better approach may be splitting the functionality
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_EXPORT functions
lines:
rule integer { \d+ {*} }
rule quote {
[ \' string_literal: '\'' \' | \ string_literal: '' \ ]
{*}
}
since these are defined as rule they skip whitespace, so the second
declaration actually forces parsing of literals like
into
The attached patch modifies mk_language_shell
a per-interp seed, set to some random value during Parrot's
initialization? This would keep any sharp edges away from users and
avoid those charming algorithmic complexity attacks (assuming
Parrot_int_rand can find sufficient randomness).
This patch starts to implement a per-interp hash seed
On Fri Sep 19 07:32:09 2008, pgerd wrote:
On Do. 18. Sep. 2008, 10:52:32, julianalbo wrote:
Is not good that pir or pasm code meaning be dependent of locale
specifics of the system.
Also in several operating systems is not the computer who is working
with some charset and encoding or
# New Ticket Created by Bruce Stockwell
# Please include the string: [perl #60682]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60682
rewrite of t/oo/subclass.t to PIR.
subclass.t | 886
and Patch Bug Report Submission Information links are
broken. They point to http://www.parrot.org/glossary.html and
http://www.parrot.org/docs/submissions.html, respectively.
--
Matt http://ftbfs.org/
# New Ticket Created by Bruce Stockwell
# Please include the string: [perl #60600]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60600
rewrite of t/oo/ops.t to PIR.
ops.t | 265
. The patch fixes this behaviour.
lu
--
Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
--- parrot-0.8.0/tools/dev/install_files.pl 2008-05-22 19:56:38.0 +0200
+++ tools/dev/install_files.pl 2008-11-17 12:10:10.0 +0100
@@ -202,8 +202,10
/10/22
needs the following patch to compile parrot. The problem appears to be
the same one already documented for icc in tools/build/c2str.pl:
# NOTE: when CONST_STRING gets used it and any macro invocations
# that it is used in *should not* be split across more than one
# line, because
On Mon, Nov 17, 2008 at 11:37:23AM -0800, Andy Dougherty wrote:
The latest version of Sun's compiler,
cc: Sun Ceres C 5.10 SunOS_i386 2008/10/22
needs the following patch to compile parrot. The problem appears to be
the same one already documented for icc in tools/build/c2str.pl
.
The remaining one is now trapping for an explicit error.
Other than that, the patch looks good. Make those changes and I'll be
glad to apply it.
I'm attaching the diff. I hope this is the correct way.
ops.t | 219
+++---
1 file
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #60634]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60634
This patch cleans up a few test files left in /tmp by the test suite.
diff -r -u
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 foul of Algorithmic
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
explicit about which exception type(s)
they're catching. This keeps other incidental exceptions from masking
bugs. The first test in t/pmc/ro.t is a good example of what to do.
You can find the exception type by acking Parrot for the exception's
message.
Other than that, the patch looks good
On Saturday 11 October 2008 14:53:53 Christoph Otto wrote:
Calling string_hash with a seed value other than the one used in src/hash.c
(3793) can cause strange and wonderful failures if the STRING is reused by
imcc.
What happens is that after the STRING's hash is computed, it's cached in
# New Ticket Created by Bruce Stockwell
# Please include the string: [perl #60546]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60546
This is rewrite of t/oo/proxy.t to PIR
proxy.t | 89
# New Ticket Created by Bruce Stockwell
# Please include the string: [perl #60550]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60550
This is a rewrite of t/oo/methods.t to PIR
methods.t | 120
# New Ticket Created by Brad Bowman
# Please include the string: [perl #60530]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60530
Hello,
I tried the first example in docs/embed.pod but it needed a few
tweaks to
# New Ticket Created by Bruce Stockwell
# Please include the string: [perl #60512]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60512
This is a rewrite of t/names.t from a perl test to a PIR test
names.t | 63
# New Ticket Created by Brad Bowman
# Please include the string: [perl #60450]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60450
A few things that rendered strangely on the web in
docs/memory_internals.pod and
# New Ticket Created by Brad Bowman
# Please include the string: [perl #60412]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60412
Misspelt is and changed in src/debug.c comments.
Corrected case of
Bernhard Schmalhofer via RT wrote:
On Mi. 05. Nov. 2008, 21:02:19, [EMAIL PROTECTED] wrote:
Could you take a look at line 182 of compiler_faq.pod?
I get a coding standard complaint because of the linelength:
Oops. I've tweaked that line to be under the limit and
the test should be passing
# New Ticket Created by Brad Bowman
# Please include the string: [perl #60364]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60364
Hi,
The pdd19_pir.pod is no longer a draft, this patch corrects the
L references
inadvertently ignores its 'hll' argument. The
attached trivial patch corrects this oversight.
p6object-hll.patch
Description: Binary data
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
it'd
# New Ticket Created by Michael Stephens
# Please include the string: [perl #60108]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60108
I've fixed many of the headings, links and anchors in Chapter 3 of the
book
attention.
Since you're proposing a patch, I'll merge 59634
into this one.
Thanks. Hopefully this time there will be some traction because there does
appear to be a bug in Perl 6, as evidenced by this one-liner:
perl6 $ ../../parrot perl6.pbc -e 'my $x = 3; $x **= 2; say $x'
3
Unless
2008/10/18 François PERRAD via RT [EMAIL PROTECTED]:
I am not really happy with this patch.
Perhaps my initial goal with the script tools/install/smoke.pl wasn't
well-known and/or understood.
Its main use case is :
- a Windows user (without parrot dev tree) downloads and installs the
setup
patch (with some fixes) in r32072, so
that the test correctly reports failures instead of simply
saying there are misnumbered tests.
Lastly, we've now reorganized the 'make test' target to make it more
obvious when there is a failure in the t/00-parrot/ or t/01-sanity/
tests, and removed the coding
OK, I've updated the patch. I've made the following assumptions:
1. I cannot load modules.
2. I cannot use subroutines.
3. I cannot use inline ops for the test counter (since that's what
is being tested)
The problem is that I've made the tests pass by assuming that the value
Sorry for the patch spam. I'm embarrassed that I didn't have this correct the
first time (hey, YOU stay home and write tests for a strange platform while
sick)
The test will now fail, but they'll fail for the correct reason: **= is being
misparsed, as pointed out earlier.
You might
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #60016]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=60016
If you do this after building parrot:
cd languages/perl6
make test
This
jerry gay wrote:
On Fri, Oct 17, 2008 at 4:00 PM, Mark Grimes [EMAIL PROTECTED] wrote:
The attached patch now includes the pir/pasm_error_output* tests in
pir. I have also added t/pmc/complex.t. Couple of issues:
1) I am not sure how to deal with pcc_sub's so I put them into
t/pmc/objects
proposing a patch, I'll merge 59634 into this one.
kid51
it may be better to forget about this patch for
the moment.
May I just suggest that the documentation be changed to state explicitly
that only one optable is allowed? (Something like the tiny attached patch?)
--
Florian,
http://openweb.eu.org/
http://www.linux-france.org/
--- docs/pct
to that label. t/pmc/resizablestringarray.t
uses this style.
Thanks Christoph. That is pretty straight forward. I'll update and
send a new patch.
when I was on my PIRifying binge, but I didn't have nearly enough
patience at the time.
Agreed. Takes quite a bit of patients, but I have put together
On Fri, Oct 17, 2008 at 4:00 PM, Mark Grimes [EMAIL PROTECTED] wrote:
The attached patch now includes the pir/pasm_error_output* tests in
pir. I have also added t/pmc/complex.t. Couple of issues:
1) I am not sure how to deal with pcc_sub's so I put them into
t/pmc/objects-pcc_sub.t
2
I am not really happy with this patch.
Perhaps my initial goal with the script tools/install/smoke.pl wasn't
well-known and/or understood.
Its main use case is :
- a Windows user (without parrot dev tree) downloads and installs the
setup of a monthly release.
- he runs this script in order
that test_more.pir doesn't export nok. It is a simple fix,
and I have included a patch.
Thanks,
Mark
test_more.patch
Description: Binary data
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 them in perl
On Thu Oct 16 17:20:00 2008, mgrimes wrote:
Hi,
I was doing some test clean up (converting perl test to pir), and I
noticed that test_more.pir doesn't export nok. It is a simple fix,
and I have included a patch.
Thanks,
Mark
Thanks, applied in r32004
--
Will Coke Coleda
/complex.t.
Two things here:
1) test n.48 passes for me. It was marked as failing for Win32.
Following patch removes the skip block.
-8---
Index: t/pmc/complex.t
===
--- t/pmc/complex.t
I'm a little reluctant to commit to any specific modifications
to optables at the moment because much of this will be significantly
refactored in the relatively near future as part of implementing
protoregexes and longest token matching into PGE.
As that's being done, I suspect we may discover
On Thursday 02 October 2008 07:35:09 NotFound wrote:
I think will be better the other way, using the return value to flag
existence, and passing a pointer to store the result. This will allow
shorter and cleaner code.
A 5% improvement in some subsystems is nice, but nothing else uses out
1 - 100 of 7120 matches
Mail list logo
