> > One of the challenges of writing embedded code is that you need to be > cognizant of careful programming vs performance cost. It is true you > could wrap the function, or the parameter to the function, and there > is a library that does exactly that, its is the ST Micro Standard > Peripheral library. Many people, myself included, find it unusable. > Not just for the wrapping/unwrapping, gratuitous structuring stuff, > but it is solving problems that do not exist.
> Just my opinion of course, > --Chuck I agree. I'm glad to see in "in print." I find even hard coding register bits, e.g. 0x01, is often easier than using some #define label that has to be looked up in a .h file. The bit pattern translates directly from the source code to the documentation for registers, whereas that #define requires an extra step to look it up, and on rare occasions is even incorrect. Don ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ libopencm3-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libopencm3-devel
