| ??? 12/04/07 15:16 Read: times |
#147852 - Portable by BIOS Responding to: ???'s previous message |
Eric !
That BIOS solution is brilliant. Actually it is widely used and yes, it is the only decent option in mid to big systems in cases like You described. The most common multitasking OS (and it is not Windows or DOS or Linux) is a very good example of this. It is really some sort of art to be able to distinguish the parts of code that can be reused. It is also another form of art to be able to put those aside in a way that they can be found later when needed. Propably 90% of all 'C' code is actually portable but it is organized in a way that prevents it from being reused. It does not matter whether You do the reusing by copy-pasting or setting up compiler flags. The result is the same - having the feet on the table and leaning backwards + one frosty. |
| 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 |