| ??? 12/04/07 08:23 Read: times |
#147839 - A good point - often missed Responding to: ???'s previous message |
Esko Ilola said:
As an example I have created a library that can drive a LCD module (diverse manufacturers) whom all seem to have the same sort of 4/8 bit interface. They may vary in display size and organization but they all seem to boil down to the identical CPU interface. This might be because they all seem to use the same driver chip... Yes, this is a point often missed by people who seem to think that only "sample code" written specifically for their particular choice of processor can be of any use. But, as you say, this is not a real restriction - some common examples: etc, etc... |
| 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 |