Hi Vasile, > If you have an 8 stack microcontroller, using inline coding is like the aer, > so > _usec_delay can be sometime much better than delay. > Library like LCD are using 3 or 4 stack level for a simple job as > displaying. > Even if you have a large memory microcontroler (talking about 16F here) > you can't use it because of stack overflowing.
It is true that the libraries are more moduler then jal04-libraries. They provide more functionality and also use more stack. But PICs are larger then in the 16f84 days too (yes, I know - not the stack of 16f pics, but there are more and more 18f's out there). And maybe my apps are specific or I have a strange coding style, but I use 16f a lot and more often run into the ram limitations and fill up the flash memory pretty fast, but haven't run into the stack limitation for over a year. But having said this: I do agree stack should always be taken into account when you design a new library. > Please reconsider. Reconsider what? My suggestion is to use delay.jal in the sampels, at level-0, so this does not affect stack use of the library. And as a general rule it is better (at least for application code) to write modular, readable code and only start optimizing when you need it. 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.
