[slf4j-dev] [Bug 93] Small glitch/inconsistency in MessageFormatter.format(..) behaviour as well as testcase

bugzilla-daemon at pixie.qos.ch bugzilla-daemon at pixie.qos.ch
Thu Jul 31 21:44:30 CEST 2008


http://bugzilla.slf4j.org/show_bug.cgi?id=93


Ceki Gulcu <listid at qos.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|                            |WONTFIX
             Status|NEW                         |RESOLVED
                 CC|                            |listid at qos.ch




--- Comment #1 from Ceki Gulcu <listid at qos.ch>  2008-07-31 21:44:30 ---
Hi Joern,

Thank you for taking the time to report this issue.

The current implementation suspends escaping if the '{' is found as
the last character of the format string.This ensures that there are
other characters following the '{' keeping the rest of the
implementation simpler. For example, the following code does not need to
be checked for out of bounds

  char delimStop = messagePattern.charAt(j + 1);

However, I agree with you that this behavior is not consistent with
what you expect. If in your implementation you would rather enforce
escaping, even if '{' is the last character of the format message,
that would be reasonable.

I rather keep the implementation simple rather than perfectly
consistent in all possible aspects. As you say, it's too much of a border case.


-- 
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the slf4j-dev mailing list