I think these libraries should be updated to save on cycles. I think this is better then readability in this case. I don't think anyone would have the need edit print.jal. If you want to keep readability, you can put the old print.jal at the bottom of the file commented out completely so someone may replace a procedure if needed.
>current dword 83832 cycles >new dword 2203 cycles that's a big difference. on 20mhz, it is 4ms compared to 0.1ms. It would take too much time to print many things on a lcd with the current print.jal Matt. On Jan 7, 1:50 pm, Joep Suijs <[email protected]> wrote: > Hi Oliver, > > > @ Joep: I haven't used print.jal much. But I have used format.jal a lot! I > > can arrange output in columns on the screen with it which helps a lot in > > many cases. That lib is useful, and it is used! :-) > > Thanks! > Format also has a bug: both sign and decimal point are not (always?) > correctly taken into account. Also there is no general 'fail' > character, like #. If there too little space, garbage is printed. And > maby refactoring in the line of print.jal might reduce memory usage. > But let's first see what happens to print.jal... > > 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.
