Mike wrote:
>
> >: (B) Need to know the root of the numeric types
>
> If it isn't obvious to everyone else, the main (only?) reason to care
> about this is when checking/specifying context/args. Assume num means
> a double-precision float.
>
> Simply put: (a) if you pass an to a function def
On Monday, November 18, 2002, at 04:54 PM, Larry Wall wrote:
: (B) Need to know the root of the numeric types
:
: Option 1:
: numeric (mostly abstract base class)
: - num
: - int
:
: Option 2:
:
: num (floating point 'num' is the base class)
: -
On Mon, Nov 18, 2002 at 11:22:00AM -0800, Michael Lazzaro wrote:
: Here are some issues we need the design team to decide.
I shall presume that I can speak for the design team. :-)
: (A) How shall C-like primitive types be specified, e.g. for binding
: to/from C library routines, etc?
:
: Op
On Monday, November 18, 2002, at 01:33 PM, Dave Whipp wrote:
my int $a is range(1000..1255) is unchecked; # auto-infer 8bit
Just to clarify: I think of the latter (C) for efficient
packing into arrays (e.g. a 5-bit range can be packed efficiently,
even though there is no 5-bit c-type): b
"Michael Lazzaro" <[EMAIL PROTECTED]> wrote
> (A) How shall C-like primitive types be specified, e.g. for binding
> to/from C library routines, etc?
>
>Option 1: specify as property
>
> my numeric $a is ctype("unsigned long int"); # standard C type
> my numeric $b is ctype("my_int32"
Here are some issues we need the design team to decide.
(A) How shall C-like primitive types be specified, e.g. for binding
to/from C library routines, etc?
Option 1: specify as property
my numeric $a is ctype("unsigned long int"); # standard C type
my numeric $b is ctype("my_int32"
