TSa:
Perhaps we
can live with the numerically lower end always beeing part
of the range, the larger one never,
I don't think so.
0 .. 5 == ( 0, 1, 2, 3, 4)
{ action } for 0 .. 5
is supposed to run for 0,1,2,3,4,5.
But '0 .. ^5' should not mean '( 0, 1, 2, 3, 4, 5)' just because
[bernhard - Mi 05. Okt 2005, 12:05:35]:
The dir 'examples/assembly' is gone in r10185.
The examples it formerly contained are either deleted or moved to
'library', 'pir' or 'pasm'.
Most of the moved examples are tested by t/examples/*.t.
Some broken examples, or not easily testable examples,
# New Ticket Created by chromatic
# Please include the string: [perl #37769]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=37769
On Tue, 2005-11-22 at 17:06 -0800, jerry gay wrote:
i've attached a patch with some
# New Ticket Created by Will Coleda
# Please include the string: [perl #37770]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=37770
src/pbc_merge.c
src/pbc_merge.c: In function 'pbc_merge_bytecode':
Hi all,
Here's a first shot at Test::More in pure PIR. It only supports plan(),
ok(), and is() (for integers, floats, strings, and PMCs) right now. If
everyone's reasonably happy, I'll check it in. Everything's pretty
straightforward here and any decent PIR hacker should be able to follow
