comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Going outside the interger limits
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Going outside the interger limits [message #41077 is a reply to message #40958] Wed, 22 September 2004 11:46 Go to previous messageGo to previous message
JD Smith is currently offline  JD Smith
Messages: 850
Registered: December 1999
Senior Member
On Wed, 22 Sep 2004 10:55:31 -0600, R.G. Stockwell wrote:

> "Lloyd Watkin" <lloyd@evilprofessor.co.uk> wrote in message
> news:c3f97ff.0409220637.380f5018@posting.google.com...
>> In the end, it turned out that I was taking fix(a float) where as what I
>> should of done is taken long(a float) as I knew I'd be going outside the
>> limit.
>>
>> Typical!
>>
>> Thanks for all the help as usual,
>>
>> Lloyd Watkin
>
> lol, i do this all the time (well i did until i outlawed the use of fix)
> That and using "for i = 0, maxint-1 do begin" instead of "for i = 0L,
> maxint-1 do begin"
>
> They should change the name of fix() to areyousureyouwanttocasttoashort()


You could always add:

COMPILE_OPT DEFINT32

to the top of your routine definitions. It would be nice if you could
do it once for an entire class or package of routines, but I think
each routine requires it. You could always @include it, for easy
change later. For me, LOGICAL_PREDICATE would also be a good
addition. I just can't bring myself to stick it at the top of every
routine. I suppose I could change my IDLWAVE templates to include
the correct incantations...

JD
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: obtaining a structure's name
Next Topic: Using GCTP in IDL instead of MAP_SET

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Oct 12 02:36:27 PDT 2025

Total time taken to generate the page: 0.72031 seconds