Re: Should a TC be allowed to remove the MAX-ACCESS restrictions of its base type?

["David T. Perkins" <dperkins@dsperkins.com>]

HI,

We've had these arguments many times in the past, with some people
changing their positions!

The most frustrating part is that no standards progress has been
made even though there are real problems (not just theoretical
ones) to be addressed, and even though there have been implemented
and demonstrated reasonable technical solutions.

I'll stop here, not wanting to start a huge fight, maybe just a
small one with Randy about his statement...
At 03:57 PM 9/3/2002 -0700, Randy Presuhn wrote:
>.... stuff cut
>Agreed, and more: The SMI shouldn't have tagged all these
>things that are simply INTEGERs.

And maybe I'm reading more into this than he means. But if the
goal is to have just "INTEGER" with no ranges, then I don't want
to be a part of that world. There, everything uses a library that
can cope with varying (even to infinity and back) size. That world
is a slow and bloated world. I can live in a world with small taxes
on the network exchanges that enhance interoperability and backwards
compatibility. But in "my scope", I want to have lean and fast
code.

Regards,
/david t. perkins