On 2/25/10, Joep Suijs <[email protected]> wrote: > > 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.
Because you are good and probably your first job is software. I'm feeling good too but my first job is hardware.Do not ask from a hardware guy to write code like a software one. I have run out of stack in my last two projects, I've noticed all highly modulised libraries like software i2c, my SMbus, even the standard LCD are using so fast 3 or 4 stack that can't even blink. If need some large display menus, communication and whatever else may be (analogic, eeprom, humidity sensor), the solution I found is regression from calling procedure in procedure to the inline coding. Maybe there is other way but I didn't found it yet. 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, That is ok. Level zero means low use in real programs, just for blinking right? Vasile -- 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.
