Hi Vasi 2011/1/8 funlw65(Vasi) <[email protected]>: > mikroElektronika guys have their own closed general libraries. After a > lot of complains about performance issue, they granted access (after > signing some papers about secrecy, of course) to two clients, Medrea > Florin and another one, to their sources. The result? Better libraries > regarding to performance and resources. And this helps their compiler > to go higher. Bugs? Yes, they are everywhere, in any kitchen. Users > helps in squashing them. What's the point here? Jallib libraries are already open, so anyone can do suggestions for specific improvements. Matt suggests that speed should be priority over other resources and you say the oposite. It is a trade-off, but I tend to be on your side (flash/ram/stack use).
What we have here is some basic point for generic libraries. Resources are ram, flash, stack and cpu cycles. Which one is the most important? I guess the one you run out of first. But that is implementation specific. So have one large core routine with lots of small stubs? Pays off when you use multiple stubs. Inline or not - depends on how often you use a statement. Speed or size? Depends on your requirments. I think there is litte problem with a dword that takes 500ms if you only print it once a day... > Maybe a documentation header for every function inside libraries can > help actual and future developers about readability. I do not object to more complex algorithms if the result is better. My point is complex algorithms are more likely to catch a bug when implemented. And on average, 60% of each bugfix also introduces a new bug. So I disagree with the view that code is only read once and clarity is not an issue. It is important and gets even more important if complexity increases. Joep -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
