| ??? 12/04/07 17:57 Read: times |
#147860 - HAL Responding to: ???'s previous message |
The hardware abstraction routines, those at the absolute lowest level that diddle the pins, are the only things that *need* to change. That's the point. A couple of lines here and there and the module is good to go. So most of the code is portable, and hence reusable. |
| Topic | Author | Date |
| How to write portable code | 01/01/70 00:00 | |
| C is a language - not a compiler | 01/01/70 00:00 | |
| PL/M | 01/01/70 00:00 | |
| Have you considered PLM2C? | 01/01/70 00:00 | |
| A good point - often missed | 01/01/70 00:00 | |
| So what's the downside? | 01/01/70 00:00 | |
| Complex code - Libraries | 01/01/70 00:00 | |
| COTS libraries versus inhouse libraries | 01/01/70 00:00 | |
| Hence portability is not such a big issue! | 01/01/70 00:00 | |
| There are downsides | 01/01/70 00:00 | |
| Portability vs. Readability/Maintainability. | 01/01/70 00:00 | |
| who gives a hoot about portability | 01/01/70 00:00 | |
| Portable by BIOS | 01/01/70 00:00 | |
| I give a hoot about portability | 01/01/70 00:00 | |
| I am definitely not arguing against "code reuse" | 01/01/70 00:00 | |
| HAL | 01/01/70 00:00 | |
| Small and easy things that may make Your day | 01/01/70 00:00 | |
| The developer is probably the biggest factor | 01/01/70 00:00 | |
| I may take issue with this one... | 01/01/70 00:00 | |
general re 'portable code' | 01/01/70 00:00 |