| ??? 12/04/07 08:33 Read: times |
#147840 - So what's the downside? Responding to: ???'s previous message |
Esko Ilola said:
Is it worth the effort? The "effort" comes in two forms: 1. Development Writing portable code requires skill, experience, careful design, and a thorough knowledge of your craft. 2. Run-Time Portable code, by its very nature, cannot use any of the tricks or special features of the architecture that could otherwise be used to enhance its performance (speed of execution and/or memory size). Therefore portable code is almost bound to be slower and/or larger than custom-tuned code. Of course, whether or not these are significant, or outweighed by the advantages, is an entirely different issue... |
| 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 |