Hi Vasi, First of all, nothing will disappear - svn keeps track of everything.
Feel free to test it and see it is usefull or should be considered a joke, due to resource usage or any other reason (like the change of the api). I put the code into /trunk/test/jal/tst_serial_format.jal, but it is actually an attempt to make some progress on print_ng after a year without modifications on this topic. Joep 2010/8/26 funlw65 <[email protected]>: > Hi Joep, > > Is good to have it, thank you! I saved it just in case :) . I will try > to test it soon. Personally, I was involved in other things, time is > short, but I guess I wasn't the target. I just hope that good things > are not disappearing ... > > Vasi > > On Aug 26, 9:30 pm, Joep Suijs <[email protected]> wrote: >> Hi guys, >> >> No response on the message below, so I guess there is no demand for >> this or other related leftovers. I will remove the related code >> shortly so there will be no loose ends. >> >> Joep >> >> 2010/6/21 Joep Suijs <[email protected]>: >> >> > Hi guys, >> >> > As a proof-of-concept, I created a new version of nformat_byte_dec() >> > and nformat_byte_dec(). They fix the faulty behavior of the old >> > procedures and are thus incompatible. I also changed the only global >> > variable left into a parameter, but that could be changed back easily. >> > So let me know what you think of this. >> >> > The new procedures are bigger than the old ones, but save a few bytes >> > of ram and two stack levels! >> > Functional changes: >> > - the routine always outputs n_tot nr of chars >> > - when the requested formatting does not fit, '#' signs are printed >> > (and no 'garbage') >> > - n2 (number of chars behind the point) can be larger than 2 (so >> > 0.0123 is supported) >> > - signed numbers don't have to reserve a space for the sign (so '-9' >> > to '99' can be formatted in 2 positions, this was '-9' to ' 9') >> >> > The output of the test program is appended to the source. Have a look >> > and see if all is like you expect. >> >> > And also, let me know what would be the best way to make this >> > procedures (and the 16 and 32 versions) available. E.g.: >> > - new functions, next to the old formatting ones (and if so, what >> > would be a good name?). >> > - as above, but mark the old format_*_dec deprecated >> > - substitute the old functions (with or without the extra parameter) >> >> > Joep >> >> > 2010/6/21 <[email protected]>: >> >> Revision: 2097 >> >> Author: jsuijs >> >> Date: Sun Jun 20 15:04:48 2010 >> >> Log: nformat_byte_dec and nformat_sbyte_dec >> >>http://code.google.com/p/jallib/source/detail?r=2097 >> >> >> Modified: >> >> /trunk/test/jal/tst_serial_format.jal >> >> >> -- >> >> 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. > > -- > 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. > > -- 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.
