Go Down

Topic: Concatenate Float w/ a String (Read 4 times) previous topic - next topic

ahref

If were talking about a project that could do with a 1280 I don't know why we are comparing it to the price of a tiny with a lot less processing power that will probably fall short anyway. Regardless. Its still my choice to throw money around and have enough power to throw floats around. I think that solves the money problem.

Your Kludge is a kludge.
Quote
A kludge (or kluge) is a workaround, a quick-and-dirty solution, a clumsy, inelegant, difficult to extend, hard to maintain yet effective and quick solution to a problem, and a rough synonym to the terms "jury rig", "Jugaad" or "jerry rig".


which leads me to backwards learning, I mean if someone sees your kludge and they aren't aware of the lack of float support they will most likely come to your desk and ask you what is going on. Instead you could enable floating support because your platform obviously needs it if you are writing that code.

Without wanting to flog a dead horse here i'll make it brief, The option to enable floats should be a part of the arduino core. Do you have any arguments to just that sentence that make it not being an option logical?

Arrch


If were talking about a project that could do with a 1280 I don't know why we are comparing it to the price of a tiny with a lot less processing power that will probably fall short anyway.

Like it has in all my projects  :smiley-roll:
Quote
Regardless. Its still my choice to throw money around and have enough power to throw floats around. I think that solves the money problem.

Well then, sticking to prototyping is ideal for you.

Quote
A kludge (or kluge) is a workaround, a quick-and-dirty solution, a clumsy, inelegant, difficult to extend, hard to maintain yet effective and quick solution to a problem, and a rough synonym to the terms "jury rig", "Jugaad" or "jerry rig".


Without saying "you should be able to already do this with sprintf()" (which makes it a workaround, not a kludge), explain how my workaround is inelegant, klumsy and difficult to extend?

Quote
which leads me to backwards learning, I mean if someone sees your kludge and they aren't aware of the lack of float support they will most likely come to your desk and ask you what is going on. Instead you could enable floating support because your platform obviously needs it if you are writing that code.


Then why not use a device that has an FPU? Hell, you could consider the entire floating point software suite for the Arduinos as a kludge.

Quote
Without wanting to flog a dead horse here i'll make it brief, The option to enable floats should be a part of the arduino core. Do you have any arguments to just that sentence that make it not being an option logical?


I tend to avoid doing floating point calculations in my projects, so I have no need to enable it. If enough people care about this lack of option and complain to the developers that it should be included, I'm not going to argue against it.

ahref

Quote
I tend to avoid doing floating point calculations in my projects, so I have no need to enable it. If enough people care about this lack of option and complain to the developers that it should be included, I'm not going to argue against it.


That is fair :). So let's get it as a valid option :D!

Krupski


It should be a documented step to enable, or like the very nice edit a checkbox. I would uncheck that box when working with tinys or unos.


Grab this file: https://github.com/krupski/arduino-1.0.3/blob/master/app/pde.jar

Backup your pde.jar file and replace it with this one. It adds a checkbox in Preferences to enable or disable floating point support (i.e. using %f).

It works with Arduino 1.0.0 to 1.0.3.
Gentlemen may prefer Blondes, but Real Men prefer Redheads!

ahref

I did this the moment I saw it krup. Many thanks for the github link though. I find it more reliable than your site :)

Go Up