What about a fully functional printf function? On Jan 12, 10:45 am, Sebastien Lelong <[email protected]> wrote: > Hi guys, > > Just by looking at the names ("format", "print"), I would expect: > > - format.jal not to print anything, but provide a way to eval things like > "%s %4.2f". Functions would return formatted strings. The fact there are > actually procedures with an output device as parameter keeps me get confused > as it's just not involved in formatting data > - print.jal being responsible for actually printing things coming from > format.jal. Maybe providing some helpers. > > I've already been explained several times, I still can't figure out why > format.jal exists (or print.jal on the other side), except that format.jal > was the original lib, and been re-written to create print.jal. If, in the > way I understand lib features based on their name, print.jal is "just" about > printing, then it doesn't add much value as it's just a matter of dealing > with pseudo-vars. I would then understanding why format.jal would also take > care of printing and print.jal would be removed, but I would also argue > format.jal isn't properly named... Please save my sould and tell whether > format.jal should really be named like that, or if it's a kind of print2.jal > :) > > About formatting, what about a thousand separator char (quot, space, > comma) and a decimal char (dot, comma) ? > > Cheers, > Seb > > 2011/1/12 Joep Suijs <[email protected]> > > > > > Hi Kiste, > > > > I believe the flaw in format.jal is that it is not being discussed in > > detail recently ;-) > > Stef made a pretty usefull library at the time, but it has some flaws > > and inconsistensies. In the first year of jallib, many libraries were > > refactored, but format.jal was such a taks that I decided to leave it > > at the time and create the more elementary print.jal. > > Last year or so there where some complaints and I worked on the > > library for some time, but the result was never assesed due to the > > lack of 'discussion in detail' as you call it. And since I have no > > strong opinion on this lib and the complaints (I don't use it), I > > redraw the modification. I guess when 'somebody' stands up and start > > working on format.jal, it would be worth while to dig into svn to look > > at my modifications. > > > > I proposed the column-arrangement because I don't see a use for the > > print_array procedures without that. > > You could be right, but I guess Matt has an opinion about this too... > > > > But if print.jal is only for unformatted output, I think both the > > fixed-point and the print_array do not belong there, but in format.jal. > > Well, an other reason for refactoring format.jal. It is probably quite > > a job to do so, but the result will be rewarding since there is much > > to improve :) > > > 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]<jallib%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/jallib?hl=en. > > -- > Sébastien Lelonghttp://www.sirloon.nethttp://sirbot.org
-- 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.
