I've revisited a nice article about embedded things, I think some issues here are quite common to jal:
http://www.embedded.com/design/networking/199904931?_requestid=39844 Here the expert says (in C language optimisation section): "Avoid long if-then-else chains. Use a switch statement or a state machine" I'm using very long if-elsif-end if jal structure (1k-2k lines or so inside the if body) with some constant flag identifiers helping to jump inside the if-elsif-endif. Switching between the program branches is using the operator action (buttons) or the process action. The question is: can the if-end if be changed with something else (case of?). There is a major benefit of using "case of" instead of long if ...end if for long programs? On my old programs I remember clearly I had big problems with such long if-end if, I had to split a long if...end if in two small parts and copy the variables within those two. thx, 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.
