Hi All,
https://docs.raku.org/language/numerics#Auto-boxing
https://docs.raku.org/language/nativetypes#Types_with_native_representation_and_size
I think I have uncovered a misunderstanding on my part.
I use to believe if you did not tell a variable
what its size was, that it was figured out on
From: chromatic <[EMAIL PROTECTED]>
Date: Mon, 27 Oct 2008 20:00:50 -0700
On Monday 27 October 2008 19:36:58 chromatic wrote:
> I think I know how to promote primitive registers to their
> autoboxed PMCs in that function; Parrot's calling conventions should take
> care of the re
On Monday 27 October 2008 19:36:58 chromatic wrote:
> I think I know how to promote primitive registers to their
> autoboxed PMCs in that function; Parrot's calling conventions should take
> care of the rest.
Fixed in r32211. All tests pass (including the TODO test I added for this).
-- c
On Monday 27 October 2008 19:26:31 Bob Rogers wrote:
> All true. But it's unfortunate that the Parrot type system considers
> "int" and "Integer" unrelated. As a result, MMD prevents autoboxing
> (when chromatic and I had expected otherwise).
I'm not sur
.sub foo :multi(String)
>.param pmc s
>
>say s
>.end
> [...]
>Which brings us to an interesting question: How can you decide what
> type to use for autoboxing before you've determined the actual sub
> you're going to call? An
us to an interesting question: How can you decide what
> type to use for autoboxing before you've determined the actual sub
> you're going to call? And how can you find the sub without having the
> correct dispatch types up front?
According to t/pmc/multidispatch.t, :multi can s
y.html?id=60124 >
I expect this code to dispatch properly; autoboxing works and :optional
parameters work, at least separately. When combined, they appear not to
work.
I think this is purely an autoboxing+MMD issue: The following
simplified version fails in the same way, even wi
# New Ticket Created by chromatic
# Please include the string: [perl #60124]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=60124 >
I expect this code to dispatch properly; autoboxing works and :optional
parameters w
l Lua maps Boolean
I don't know if autoboxing (maps Boolean) has a sense and how tests it.
HLL maps aren't yet fully implemented in all places.
François
leo
> I take inspiration in code of Tcl and Amber.
My inspiration for the Amber PMCs was from the PMCs of Lua and Tcl :-)
Roger.
I try to update and test Lua PMC.
I take inspiration in code of Tcl and Amber.
It's OK for these 2 PMC :
pmclass LuaNumber hll Lua maps Float
pmclass LuaString hll Lua maps String
But for :
pmclass LuaBoolean hll Lua maps Boolean
I don't know if autobo
11 matches
Mail list logo
