Updates:
Status: WontFix
Comment #2 on issue 128 by jsuijs: print_string early termination
http://code.google.com/p/jallib/issues/detail?id=128
2010/5/30 m...@watty <[email protected]>:
So I vote
1) Optional and default is no terminal
2) User defined, 0 for C fans and 255 recommended for reading from
Flash/EEPROM / non C libraries.
2010/5/30 William <[email protected]>:
Let me see if I can re-state the current behavior:
case 1: print_string_terminator is not defined: the code simply
loops thru the string based whatever 'count(str)' returns.
case 2: print_string_terminator is defined: then the code checks and
will terminate early if the 'terminator' is seen.
This is great, since as you say above, mostly this routine is used for
printing constants. Furthermore, in the less-common case, all you
have to do is to define the terminator and the code works fine.
So, my preference - leave the code alone. Especially since we know it
triggers buggy code in the most recent 'released' (not beta) compiler:
2.4m.
2010/5/31 Sebastien Lelong <[email protected]>:
I'm also in favor of letting the code like it is now, following what
William
and Mike said.
--
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.
