On Tue May 20 15:08:28 2008, bacek wrote:
> On Tue May 20 13:18:36 2008, [EMAIL PROTECTED] wrote:
> >
> > This is correct. PMC_*_val must die.
>
> I've created patch with replacing PMC_int_val with SELF.get_integer().
> It's attached to ticket as integer2.diff
>
Applied as r27700, thanks.
Jona
On Tue May 20 13:18:36 2008, [EMAIL PROTECTED] wrote:
>
> This is correct. PMC_*_val must die.
I've created patch with replacing PMC_int_val with SELF.get_integer().
It's attached to ticket as integer2.diff
--
Bacek.
There is a patch for src/pmc/integer.pm to use SELF.get_integer()
instead of PMC_int_val.
Index: src/pmc/integer.pmc
===
--- src/pmc/integer.pmc (revision 27652)
+++ src/pmc/integer.pmc (working copy)
@@ -200,7 +200,7 @@
*/
V
On Tuesday 20 May 2008 13:05:43 Will Coleda wrote:
> The original problem description is a little off: this works for core
> Integer type, but not for the parrotObject subclass.
>
> I was able to use gdb to break in the function called by the cmp op,
> and then step through to find which actual fu
The original problem description is a little off: this works for core
Integer type, but not for the parrotObject subclass.
I was able to use gdb to break in the function called by the cmp op,
and then step through to find which actual function this was being
sent to via MMD. It was using Integer's
# New Ticket Created by Vasily Chekalkin
# Please include the string: [perl #54474]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=54474 >
Parrot's op cmp doesn't work for integers.
$ cat v.pir
.sub main :main
$P99 =
