On Tuesday 22 July 2008 21:58:10 Mark Glines wrote: > Integer is a good example of the problem, actually. > > The internal storage format doesn't change,
It certainly can. I imagine that Kea-CL's Integers autopromote to BigInts (or whatever the name is), and that might require a certain precision size. > but the methods you can call > on it definitely will. HLLs wrap the Integer class with their own > subclasses, so that they have methods they can call on integers, which > are expected by the HLL. > > But when your perl6 function passes a Perl6Int to a TCL function, TCL > HLL code code will try to access the integer, but it's not a TclInt, > its a Perl6Int! The value itself is fine, but the methods it expects > to find will not be there. Hence the need for conversion/mapping. Boundaries do have to be somewhat explicit; I agree. -- c
