Difference between revisions of "BoostC tiny Wiki"

From OpenCircuits
Jump to navigation Jump to search
Line 24: Line 24:
  
 
=== Standard C Issues ===
 
=== Standard C Issues ===
 +
 +
==== Use a Lint Program ====
 +
Has anyone configured one for BoostC?
 +
 +
==== Read This ====
 +
[http://en.wikipedia.org/wiki/C_Traps_and_Pitfalls C Traps and Pitfalls From Wikipedia, the free encyclopedia]  Note that there is a free download or a longer ( for purchase ) book.
 +
  
 
==== Links ====
 
==== Links ====

Revision as of 08:04, 12 January 2009

Introduction

This is the very beginning of a Wiki for BoostC. Its organization will probably change a lot in the near future ( if we can get the free labor required ). It may move to the SourceBoost site if they want to host it. Since BoostC is proprietary it may be inappropriate for it to grow too big here unless we can find some explicit support for it. For now here it is.


Tips/Tricks/Gotchas

Watch out for set-bit!

The function set-bit() is almost right, but it should be set_bit(). This and similar errors are subtraction, and the result is error messages ( how about a sample ) that are not very helpful.

Rebuild It

Sometimes I have been able to get rid of odd errors by forcing a rebuild by erasing all but the project file and the .c and .h files. The manual suggests that Ctrl+F7 or Ctrl+build command do pretty much the same thing.

Subroutine signatures

Often we have several versions of a subroutine with different signatures ( set and type of call arguments ) Try to check that you are calling the version you want. Casting may help.



Standard C Issues

Use a Lint Program

Has anyone configured one for BoostC?

Read This

C Traps and Pitfalls From Wikipedia, the free encyclopedia Note that there is a free download or a longer ( for purchase ) book.


Links

Optimization

As a general rule it has been observed that many programmers spend too much time on optimization and that often the compiler can do a better job than the programmer. Often readability of the code suffers for "optimizations" that do not really optimize anything. That said, it is worthwhile to optimize the algorithm. C does not know the purpose of the code, the programmer should, the compiler can only optimize the code in doing what you said, not what you want.

Questions:

Optimizations that Seem Not to Work