In article <[EMAIL PROTECTED]>, Adam
Kennedy <[EMAIL PROTECTED]> wrote:
> Nobody would care about dependencies if they never failed (except for
> the issue of installation time).
I have a couple of clients that are very skittish about outside
dependencies in general. They have to get thrid-part
+=item * the C operator (less than, equal, or greater) ... The
+C<< <=> >> operator's semantics are unchanged except that it returns
+and Order value as described above.
typo alert: "an Order value" ... right?
a
--
Andy Bach, Sys. Mangler
Internet: [EMAIL PROTECTED]
VOICE: (608) 261-5738 FAX
# New Ticket Created by Ron Blaschke
# Please include the string: [perl #39842]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39842 >
Attached patch updates PLATFORMS with the number of failing tests on my
Windows XP box w
Applied as r13307.
Still needs some tweaking, e.g. fix the failing past.t, but good enough
for now.
leo
# New Ticket Created by Matt Diephouse
# Please include the string: [perl #39843]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39843 >
As of right now, Tcl has some failing tests skipped, some todo'd, and
other simply f
On 7/15/06, Ovid <[EMAIL PROTECTED]> wrote:
I don't particularly like that this is a silent failure, but I'm not sure of a
robust way to fix that. In any event, I reread the docs a couple of times
before I realized I was being stupid. That suggests to me that this little nit
could be improve
On 7/15/06, Jonathan Rockway <[EMAIL PROTECTED]> wrote:
What's the reasoning behind accepting an array, anyway?
Convenience. You almost always use can_ok() with a list of methods.
It also makes calculating the plan a little easier for it to be one
test.
I recall waffling around on the interfa
On 7/15/06, Jonathan Rockway <[EMAIL PROTECTED]> wrote:
Worse, it's inconsistent with the rest of the API:
ok$foo == $bar, $REASON;
is$foo, $bar, $REASON;
is_deeply $foo, $bar, $REASON;
And then this:
skip $REASON, $num;
Sadly, it would be hard to change that since so many
Miyagawa noticed that the changes to Test::Builder::Tester's
test_fail() in 0.63 broke Test::Exception and probably plenty others.
The change broke backwards compat and should not have been accepted.
So here's an emergency release to fix that.
0.64 Sun Jul 16 02:47:29 PDT 2006
* 0.63's chan
I'm looking into this issue and would like to ask for some advice.
I have added the following platform dependent functions.
int Parrot_math_isnan(double)
int Parrot_math_finite(double)
On Win32 the implementation is simple because the IEEE recommended
functions _finite and _isnan are supported.
On Sun, Jul 16, 2006 at 02:53:08AM -0700, Michael G Schwern wrote:
> Miyagawa noticed that the changes to Test::Builder::Tester's
> test_fail() in 0.63 broke Test::Exception and probably plenty others.
> The change broke backwards compat and should not have been accepted.
>
Bleadperl has been upg
Thanks, applied as r13316.
Thanks, applied as r13316.
"Will Coleda via RT" schreef:
> Thanks, applied as r13316.
Twice?
3c3
< Xref: nntp.perl.org perl.perl6.internals:34222
---
> Xref: nntp.perl.org perl.perl6.internals:34223
7c7
< Received: (qmail 22397 invoked from network); 16 Jul 2006
15:09:07 -
---
> Received: (qmail 22778 invoked from net
On 7/15/06, Guest via RT <[EMAIL PROTECTED]> wrote:
Also, is Parrot::Config no more? Can you please tell me what has
replaced it?
Thanks!
Swaroop
C is generated by C. so you won't
find it in a fresh working copy. you'll see it under C, which
may mean you need to add a line like C to your code
# New Ticket Created by Will Coleda
# Please include the string: [perl #39850]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39850 >
To de-confuse and cut back on one of the most common recent FAQs:
1) Create a stub modul
# New Ticket Created by Ron Blaschke
# Please include the string: [perl #39846]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39846 >
Problem
dynpmc.pl uses interpolated quotes to set up compiler and linker
flags, whic
mdiep wrote:
> Trying to use an Iterator with a NameSpace makes Parrot segfault:
>
>mini:~/Projects/parrot mdiep$ cat test.pir
>.sub main :main
> .local pmc iter, ns
> ns = get_namespace
>
> iter = new .Iterator, ns
>loop:
> unless iter goto loop_end
> $P0 = s
# New Ticket Created by Matt Diephouse
# Please include the string: [perl #39851]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39851 >
Switching HLLs with C< .HLL > doesn't reset the namespace. This leads
to some confus
# New Ticket Created by Matt Diephouse
# Please include the string: [perl #39852]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=39852 >
In order to pass some [namespace children] tests, I added this to the
top of runtime
David Wheeler wrote:
> On Jul 12, 2006, at 03:41, Gabor Szabo wrote:
>
>> perl -MModule -e'print $Module::VERSION'
>
> I have this alias set up:
>
> function pv () { perl -M$1 -le "print $1->VERSION"; }
>
> I think that calling ->VERSION is more correct.
I am sure this discussion has happene
* Graham Barr <[EMAIL PROTECTED]> [2006-07-17 02:00]:
> perl -MDBI\ 999
> DBI version 999 required--this is only version 1.50.
> BEGIN failed--compilation aborted.
You can use an equals sign instead of a space, there, which makes
it a little easier to type:
perl -MDBI=666 -e1
Regards,
--
#A
From: "Matt Diephouse via RT" <[EMAIL PROTECTED]>
Date: Sun, 16 Jul 2006 14:37:39 -0700
mdiep wrote:
> Trying to use an Iterator with a NameSpace makes Parrot segfault:
>
>mini:~/Projects/parrot mdiep$ cat test.pir
>.sub main :main
> .local pmc iter, ns
>
Author: larry
Date: Sun Jul 16 18:38:14 2006
New Revision: 10248
Modified:
doc/trunk/design/syn/S05.pod
Log:
Incorrect P5 syntax spotted by scw++.
Modified: doc/trunk/design/syn/S05.pod
==
--- doc/trunk/design/syn/S0
Author: larry
Date: Sun Jul 16 18:58:53 2006
New Revision: 10250
Modified:
doc/trunk/design/syn/S03.pod
doc/trunk/design/syn/S04.pod
doc/trunk/design/syn/S06.pod
Log:
Renamed .id to .valid as a pun on "value id".
Modified: doc/trunk/design/syn/S03.pod
==
Hi,
I have been working on trying to make reenterant and/or thread-safe. There
are couple of things that have come up which might make it difficult to make
the existing implemention thread-safe/re-entrant.
The current implementation is implemented using Flex and YACC. Flex
implementation has li
Hi,
Please disregard the previous mail. Hit the wrong shortcut key!!
I have been working on trying to make reenterant and/or thread-safe. There
are couple of things that have come up which might make it difficult to make
the existing implementation thread-safe/re-entrant.
The current implementa
在 2006/7/16 下午 11:57 時，Vishal Soni 寫到：
a. A clean implementation rather than a prototypish implementation
I think that the lemon+re2c, being the more modern parsing tools,
will make refactoring/hacking considerably easier. Whilst you are
converting the current IMCC implementation into
> On Mon, 17 Jul 2006 02:24:37 +0200, "A. Pagaltzis" <[EMAIL PROTECTED]>
> said:
> * Graham Barr <[EMAIL PROTECTED]> [2006-07-17 02:00]:
>> perl -MDBI\ 999
>> DBI version 999 required--this is only version 1.50.
>> BEGIN failed--compilation aborted.
> You can use an equals sign in
Shlomi Fish wrote:
On Friday 07 July 2006 18:39, Andy Lester wrote:
Those who disagree with Shlomi on licenses are small-headed and
ignorant. Got it.
Keep digging that hole, Mr. Fish!
That's not what I said or meant. What I meant was that someone here said and I
quote:
http://www.mail-ar
> I do not think that prototype means what you think it means.
It means what I think it means. Same syntax as we have currently, no.
You would have to do this:
my @methods = qw(foo bar baz)
can_ok($object, @methods, 'reason')
Instead of:
can_ok($object, qw(foo bar baz), 'reason')
Note that i
I retract my previous comment. My prototype was, in fact, completely
bogus :)
Let's make that array a reference to a list and everyone will be happy:
can_ok($object, [qw(foo bar baz)], 'reason');
Hopefully that works and makes sense. If !ref $_[1], then just treat it
as a single method name.
On 7/16/06, Jonathan Rockway <[EMAIL PROTECTED]> wrote:
I retract my previous comment. My prototype was, in fact, completely
bogus :)
Let's make that array a reference to a list and everyone will be happy:
can_ok($object, [qw(foo bar baz)], 'reason');
Hopefully that works and makes sense. If
33 matches
Mail list logo
