U++ forum: Welcome to the forum

Status & Roadmap

Authors & License

Funding Ultimate++

Search on this site

Search in forums

Home » U++ Library support » U++ Core » Value: why not float support?

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: Value: why not float support? [message #30208 is a reply to message #30204]

Wed, 15 December 2010 16:41

kohait00 is currently offline

kohait00
Messages: 939
Registered: July 2009
Location: Germany

Experienced Contributor

it's not the problem whith receiving..
on receive, i could destinguis if it's a float, or a double, and map both to use Value double..

but since the API uses Value directly, which is unbelievably easy. it determines what to send by simply checking the type.

nevertheless, it's important to differ them, since there are old target devices that only understand spec 1.0, which only has float. and newer devices also support spec 1.1 double as extra type, and maybe even expect it for some parameters, while still demanding float for some other..and how to destinguish them?

hope to have cleared it up a bit (and a bit of a bit convinced you Wink

Wink

i still could use RichValue<float>, and all the stuff for my own, but it would lack things like Value::IsNumber() and the implicit conversions, which are upp gloabl, but are reaaly appealing..

please, rethink it, float is an own type, just as int64, even if on many systems its breaks down to double in assembler/cpu arch, but compiler still differs them..

Report message to a moderator

Send a private message to this user

[Message index]

		Value: why not float support? By: kohait00 on Mon, 30 August 2010 10:54
		Re: Value: why not float support? By: mirek on Tue, 31 August 2010 15:49
		Re: Value: why not float support? By: kohait00 on Tue, 31 August 2010 16:11
		Re: Value: why not float support? By: mirek on Tue, 31 August 2010 18:49
		Re: Value: why not float support? By: kohait00 on Tue, 31 August 2010 22:02
		Re: Value: why not float support? By: gprentice on Wed, 01 September 2010 13:52
		Re: Value: why not float support? By: kohait00 on Wed, 01 September 2010 16:13
		Re: Value: why not float support? By: mirek on Thu, 02 September 2010 09:40
		Re: Value: why not float support? By: kohait00 on Thu, 02 September 2010 11:24
		Re: Value: why not float support? By: mirek on Mon, 06 September 2010 10:40
		Re: Value: why not float support? By: kohait00 on Mon, 06 September 2010 11:54
		Re: Value: why not float support? By: kohait00 on Mon, 13 December 2010 15:47
		Re: Value: why not float support? By: mirek on Wed, 15 December 2010 16:15
		Re: Value: why not float support? By: kohait00 on Wed, 15 December 2010 16:41
		Re: Value: why not float support? By: rylek on Mon, 20 December 2010 23:08
		Re: Value: why not float support? By: kohait00 on Tue, 21 December 2010 08:20
		Re: Value: why not float support? By: mirek on Fri, 24 December 2010 12:39
		Re: Value: why not float support? By: kohait00 on Fri, 24 December 2010 13:55
		Re: Value: why not float support? By: mirek on Sat, 25 December 2010 10:48
		Re: Value: why not float support? By: kohait00 on Sun, 26 December 2010 11:28
		Re: Value: why not float support? By: mirek on Mon, 27 December 2010 13:20
		Re: Value: why not float support? By: kohait00 on Mon, 27 December 2010 14:28
		Re: Value: why not float support? By: mirek on Mon, 27 December 2010 14:44
		Re: Value: why not float support? By: kohait00 on Tue, 28 December 2010 13:47
		Re: Value: why not float support? By: kohait00 on Mon, 07 March 2011 14:31
		Re: Value: why not float support? By: mirek on Mon, 07 March 2011 23:04
		Re: Value: why not float support? By: kohait00 on Tue, 08 March 2011 08:33

Previous Topic:	Core/Path.cpp: the limitation of GetCurrentDirectory for POSIX
Next Topic:	InitCaps() proposal

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

PDF

]

Current Time: Sat Jul 05 14:49:33 CEST 2025

Total time taken to generate the page: 0.05372 seconds