Hi Matt,
> okay, thanks for the explanation. Would other conversions to 15 bits
> possibly cause problems? For instance, something being put on the stack
> beyond 32k (via 16-bit variable) and then not being able to be accessed by
> a 15-bit variable? Or, not enough stack space appearing to be present,
> causing an overflow?
The stack is part of the lower regions of the global address space in the
SCI memory model, so it won't have any problems of this kind, but
issues of this kind have traditionally been causes of interesting
problems for object pointers.
> If not, I won't report things loss of precision warnings that look like
> this. If it's a possibility, then I'll continue. :)
I'm pretty sure there's a large number of bit info losses which 'lint'
will point out. A few bugs might be hidden in there, but we'd
have to wade though a lot of code to find them.
Still, this might be worthwhile if you feed those lint reports in small
portions...
llap,
Christoph
