 vote
 |
|
A guide for the serious C programmer...
This guide mainly focuses prime issues that are involved in writing professional code, which is very efficient both in terms of space and time as well as be readily ported, to different systems with minimal changes. Writing portable code is an area, which is not paid much heed in the initial period of project. The code might work on the developer's system architecture but once it goes to field, bugs began to raise their ugly heads. Although this way minimizes the product's time to market, it also increases the overall time until final product maturity. The best approach for any developer is to avoid bugs in the first place.
| | |
| |
|
|