Re: unsigned int ? (was: 16 bit images?) [message #13259] |
Thu, 29 October 1998 00:00 |
korpela
Messages: 59 Registered: September 1993
|
Member |
|
|
In article <MPG.10a0dc4d233f00db9896e3@news.frii.com>,
David Fanning <davidf@dfanning.com> wrote:
>> does this mean they'll introduce a new TYPE value and shift
>> strings, structures, pointers, etc. one up? "Oh jemineh !" (german) that
>> would mean a lot of rewriting ...
>
> Nein. The new unsigned (16-bit) integer is type 12, followed
> by the 32-bit unsigned integer as type 13. Then the 64-bit
> integer at 14, with the new 64-bit unsigned integer as type 15.
It does mean a lot of "Unsupported data type" messages from my LINKIMAGEd
stuff once I start using the new types. I don't suppose we can convince them
to put an IDL_VERSION define in "external.h".
Eric
--
Eric Korpela | An object at rest can never be
korpela@ssl.berkeley.edu | stopped.
<a href="http://sag-www.ssl.berkeley.edu/~korpela">Click for home page.</a>
|
|
|
Re: unsigned int ? (was: 16 bit images?) [message #13268 is a reply to message #13259] |
Wed, 28 October 1998 00:00  |
davidf
Messages: 2866 Registered: September 1996
|
Senior Member |
|
|
Note: A copy of this article was e-mailed to the original poster.
Martin Schultz (mgs@io.harvard.edu) writes:
> Hi David,
>
> does this mean they'll introduce a new TYPE value and shift
> strings, structures, pointers, etc. one up? "Oh jemineh !" (german) that
> would mean a lot of rewriting ...
Nein. The new unsigned (16-bit) integer is type 12, followed
by the 32-bit unsigned integer as type 13. Then the 64-bit
integer at 14, with the new 64-bit unsigned integer as type 15.
Wow! 15 data types. Can't say RSI isn't listening to
someone! :-)
Cheers,
David
----------------------------------------------------------
David Fanning, Ph.D.
Fanning Software Consulting
E-Mail: davidf@dfanning.com
Phone: 970-221-0438, Toll-Free Book Orders: 1-888-461-0155
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|