| ??? 11/16/06 13:24 Read: times |
#128085 - Why floating point? On an 8051? Responding to: ???'s previous message |
Hello
Lines like this I try to avoid #define F40TH_OF_SECOND TMR_OV_SEC * 0.025 isn't #define (F40TH_OF_SECOND TMR_OV_SEC / 40) the same? No it isn't. Many years ago I remember that on a PC (Microsoft C Compiler Version 2) a header file had one float constant in it, that increased the code size sigificantly, because the floating point library must be linkes to the application. On a PC maybe not a problem, but in an embedded system? Using 0.025 where /40 may do the same job in plain integer? Just think about it. Best regards |
| Topic | Author | Date |
| SDCC how to | 01/01/70 00:00 | |
| erm dunno but | 01/01/70 00:00 | |
| Errr | 01/01/70 00:00 | |
| Aside: XTAL | 01/01/70 00:00 | |
| no no | 01/01/70 00:00 | |
| Missing the point | 01/01/70 00:00 | |
| basic C | 01/01/70 00:00 | |
| preprocessor does not do it! | 01/01/70 00:00 | |
| Thanks Andy | 01/01/70 00:00 | |
| Why floating point? On an 8051? | 01/01/70 00:00 | |
| yeah | 01/01/70 00:00 | |
| preprocessor does not do it! | 01/01/70 00:00 | |
| sorry but its still not working | 01/01/70 00:00 | |
| expand and see | 01/01/70 00:00 | |
| Not quite... | 01/01/70 00:00 | |
| Do it by hand! | 01/01/70 00:00 | |
| ... or let the preprocessor do it for you | 01/01/70 00:00 | |
| to make things more clear | 01/01/70 00:00 | |
| Show your expansion! | 01/01/70 00:00 | |
| preprocessor output | 01/01/70 00:00 | |
| what you miss ... | 01/01/70 00:00 | |
| I don't understand your point, but... | 01/01/70 00:00 | |
| finally I found | 01/01/70 00:00 | |
| you are trying to be too good | 01/01/70 00:00 | |
| I'd guess.... | 01/01/70 00:00 | |
| wow | 01/01/70 00:00 | |
| I know that, but they are similar enough to .. | 01/01/70 00:00 | |
one more time | 01/01/70 00:00 |