Home » U++ Library support » U++ Core » Value: why not float support?
Re: Value: why not float support? [message #30392 is a reply to message #30391] |
Mon, 27 December 2010 14:44   |
 |
mirek
Messages: 14263 Registered: November 2005
|
Ultimate Member |
|
|
kohait00 wrote on Mon, 27 December 2010 08:28 | i dont mind handling float as double in cpu context, in functions etc. but in my case, sending and receiving is done with distinct types, float and double, unfortunately not interchangeable, it's compareable to storing things .
well, my problem is actually, that i wanted to use Value as a cool implicit convertable container for arbitrary values (which it is). to save me the hassle of converting them manually, since a lot is already present. but lacking float makes it difficult to use in my case ofcorse. i might need to specify own converters which support float as well beeing a RichValue<>.
use case is indeed: an OSC Method handler receives i.e a Value as parameter, which is to be sent as float: so, if it is double, its converted, if it is int, also, if it's a String, it's tried to be parsed. etc.. thus the interface is really versatile and forgiving.
so i can set up different controls, that 'generate' internally different types (editfield a String, Option a bool/int value) but are sent as float etc.. so i dont need to care about types inside the controls already. i simply specify which type the OSC message should finally be sent as.
|
Well, if I understood well what you have just wrote, I see it as argument NOT TO introduce 'float' into Value... You can put float to Value now (as double). And you have to know the true signature of OSC method anyway, so that you can convert all parameters.
So introducing float would be no advantage here.
Mirek
|
|
|
 |
|
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
|
Goto Forum:
Current Time: Tue Jul 01 06:30:50 CEST 2025
Total time taken to generate the page: 0.03286 seconds
|