comp.lang.idl-pvwave archive: archive » Recognizing double precision?

Home » Public Forums » archive » Recognizing double precision?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Recognizing double precision? [message #56164]

Fri, 05 October 2007 08:12

wlandsman
Messages: 743
Registered: June 2000

Senior Member

About once a year I receive a complaint about my code because someone
inputs a Julian date like this

IDL> jd = 2441636.1

and then gets mysterious results because the value of jd is
"truncated"

IDL> print, jd, f='(f10.2)'
2441636.00

So it would it be reasonable to request that the IDL compiler
recognize a number as double precision, if it has too many digits to
be stored as a floating point number? After all, IDL does do
something like this (in default mode) for short and long integers:

IDL> a = 32767 & help,a
A INT = 32767
IDL> a = 32768 & help,a
A LONG = 32768

I can't imagine how adding this capability would break existing code.

Does anyone know if other interpreted languages can recognize a double
precision number when they encounter one? Thanks, --Wayne

Report message to a moderator

[Message index]

		Recognizing double precision? By: wlandsman on Fri, 05 October 2007 08:12
		Re: Recognizing double precision? By: edward.s.meinel@aero. on Wed, 10 October 2007 11:21
		Re: Recognizing double precision? By: R.G.Stockwell on Wed, 10 October 2007 08:53
		Re: Recognizing double precision? By: edward.s.meinel@aero. on Wed, 10 October 2007 07:07
		Re: Recognizing double precision? By: R.G.Stockwell on Tue, 09 October 2007 08:50
		Re: Recognizing double precision? By: Maarten[1] on Tue, 09 October 2007 08:24
		Re: Recognizing double precision? By: edward.s.meinel@aero. on Tue, 09 October 2007 08:11
		Re: Recognizing double precision? By: R.Bauer on Wed, 24 October 2007 11:15

Previous Topic:	large info structure?
Next Topic:	Read data from SQL data base?

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Nov 29 23:56:55 PST 2025

Total time taken to generate the page: 2.00282 seconds