Re: Ranges and (non)static constraints

"Jeffrey R. Carter" <spam.not.jrcarter@xxxxxxxxxxxxxxxx> writes:

Dmitry A. Kazakov wrote:
Actually it is not the machine which cannot, but the compiler. Why
should I
care if an integer would fit a machine word?

I agree. GNAT has gone a little ways in this direction, providing 64-bit
integers on 32-bit machines. If I ever get around to defining NINA, it
will accept any range for integer types. Of course, if you make them too
big, objects of the type may raise Memory_Exhausted. There would be ways
to create integer types that correspond to those supported by the HW,
where that's important.

What's NINA?

I think you're on the right track, here. The goal should be (1) the
program can use arbitrarily large integers (up to the memory limit), as
in Lisp et al, and (2) if you don't need that, you don't pay any
efficiency cost (no distributed overhead). I don't know of any language
that achieves both.

If I say:

type T is range 1..1_000_000;
X : constant T := ...;
Y : constant T := ...;
Z : constant T := (X + Y) / 2;

it is implementation dependent whether or not the calculation of Z
overflows. That's bad. (But no implementations overflow in that case,
so nobody cares, and people write such things all the time.)

If I say:

type T is range 1..1_000_000_000_000;

some implementations fail at compile time, and some do not. That's bad,
too. I ought to be allowed to say, portably:

type T is range 1..10**100;

... And there'd be type Unbounded_Integer, providing
use of the unbounded-integer library used by the compiler.

Well, I'll quibble with your names, here. When God created the
integers, He didn't say they stop at 2**31-1 or 2**64 or whatever!
The term "integer" (or the abbreviation "int") ought to mean the true
unbounded integers. Names like Unbounded_Integer and _universal_integer
are an abomination. ;-)

- Bob
.

Relevant Pages

  • Re: Revisit: List list = new ArrayList();
    ... Collection does not make it clear whether duplicates are allowed or not, ... The JDK does not provide any direct implementations of this interface: ... Collection OTOH is to be used as argument to functions which do not care ...
    (comp.lang.java.programmer)
  • Re: Tough (for me) regex case
    ... I had *no idea* that there were different implementations of "regular ... But I simply don't care about that. ... newsgroup are generally more interested in the computing problem than ... in some kind of whizzing match between two competing ideologies. ...
    (comp.lang.perl.misc)
  • Re: size of object
    ... >> For most implementations, the size of an object is the ... >> members, plus one word for the vtable, plus one word for ... >> But I still want to know why you care. ... What's with the arogant attitude, ...
    (comp.lang.cpp)
  • Re: Stack growth direction to thwart buffer overflow attacks
    ... >> Frankly i do not care about 'C99' since they don't deliver any software. ... You are complaining about ISO/ANSI standards beeing fuzzy and mayebe even wrong ... Then the code should be written with broken implementations in mind ... like ISO did with their ISO campain during the 90's. ...
    (comp.security.unix)
  • Re: Stack growth direction to thwart buffer overflow attacks
    ... >> Frankly i do not care about 'C99' since they don't deliver any software. ... You are complaining about ISO/ANSI standards beeing fuzzy and mayebe even wrong ... Then the code should be written with broken implementations in mind ... like ISO did with their ISO campain during the 90's. ...
    (comp.security.misc)