[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: uint(), uintarr() calls
- Subject: Re: uint(), uintarr() calls
- From: davidf(at)dfanning.com (David Fanning)
- Date: Fri, 20 Oct 2000 14:13:53 -0600
- Newsgroups: comp.lang.idl-pvwave
- Organization: Fanning Software Consulting
- References: <39F0A0F8.F1F69842@nssl.noaa.gov>
- Xref: news.doit.wisc.edu comp.lang.idl-pvwave:21809
Edward Spencer (firstname.lastname@example.org) writes:
> I'm working on compiling some code in IDL 5.1. This code apparently
> compiled and ran correctly on the Linux box it was developed on, but
> when I try to compile it on a Sun, the compiler gets caught on calls to
> uint() and uintarr()...
> field_header = uintarr(30) and
> po = uint(5) are some of the lines in question...
> In fact they are two of the five lines of code in the entire program
> which call either of those functions.
> I checked the documentation to find functions that might have a similar
> use in case the uint functions are too new, but the 5.1 documentation
> does not mention these calls or anything related to them.
> I'm guessing that they are meant to be built in functions, as opposed to
> defined elsewhere in the code. If anyone can point me in the right
> direction here I would appreciate it.
These are unsigned integer data types, which were introduced
in IDL 5.2. There is nothing equivalent in IDL 5.1. Depending
upon the application, you might be able to get along with
regular signed integers.
David Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438 E-Mail: email@example.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155