Hi,
it would be great to have configuration macro to enable/disable using float arithmetic in base driver's interfaces (BaseSensor and so on) to use EX on small processors with NIL.
Using float optional
- RoccoMarco
- Posts: 655
- Joined: Wed Apr 24, 2013 4:11 pm
- Location: Munich (Germany)
- Has thanked: 83 times
- Been thanked: 67 times
- Contact:
Re: Using float optional
Hello there.
I totally missed this post. I'll think about it. The point is that without floating point the whole concept of cooked data would became meaningless.
I totally missed this post. I'll think about it. The point is that without floating point the whole concept of cooked data would became meaningless.
Ciao,
RM
RM
- RoccoMarco
- Posts: 655
- Joined: Wed Apr 24, 2013 4:11 pm
- Location: Munich (Germany)
- Has thanked: 83 times
- Been thanked: 67 times
- Contact:
Re: Using float optional
Does it mean we should implement fixed point algebra? I am not so convinced about that.
Ciao,
RM
RM
Re: Using float optional
At least not use float in raw functions, in this case cooked and float will not be linked
Vitaly
- RoccoMarco
- Posts: 655
- Joined: Wed Apr 24, 2013 4:11 pm
- Location: Munich (Germany)
- Has thanked: 83 times
- Been thanked: 67 times
- Contact:
Re: Using float optional
As far as I know float is not used in raw functions...
Do you have seen float in some getRaw?
Do you have seen float in some getRaw?
Ciao,
RM
RM
Who is online
Users browsing this forum: No registered users and 9 guests