Re: [classlib]bug-to-bug compatibility j.u.Formatter

2006-07-26 Thread Richard Liang
Stepan Mishura wrote: On 7/25/06, Richard Liang wrote: Hello All, As we have further discussion about our Compatibility issues, I'd like to summarize this particular problems and ask for comments. Thanks a lot. If we pass a null to j.u.Formatter.Formatter(Appendable a), when we try to get t

Re: [classlib]bug-to-bug compatibility j.u.Formatter

2006-07-26 Thread Tim Ellison
On 25/07/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: I've tried your test - it fails indeed. Strange, such an obvious violation of the spec by RI... +1 for filing JIRA and preserving our behavior. I agree. Regards, Tim -- Tim Ellison ([EMAIL PROTECTED]) IBM Java technology centre, UK. --

Re: [classlib]bug-to-bug compatibility j.u.Formatter

2006-07-25 Thread Stepan Mishura
On 7/25/06, Richard Liang wrote: Hello All, As we have further discussion about our Compatibility issues, I'd like to summarize this particular problems and ask for comments. Thanks a lot. If we pass a null to j.u.Formatter.Formatter(Appendable a), when we try to get the destination of the for

Re: [classlib]bug-to-bug compatibility j.u.Formatter

2006-07-25 Thread Spark Shen
Anton Luht 写道: Hello, And there are places RI behaves irrational and not compatible with RI. You mean RI behaves not compatible with spec? :) Hi, Anton: *Irrational* may be not a good word, is *illogical *better?. :-) In some places, RI does behave differently from RI. This can be proved

Re: [classlib]bug-to-bug compatibility j.u.Formatter

2006-07-25 Thread Alexei Zakharov
Hi Richard, I've tried your test - it fails indeed. Strange, such an obvious violation of the spec by RI... +1 for filing JIRA and preserving our behavior. Regards, 2006/7/25, Richard Liang <[EMAIL PROTECTED]>: Hello All, As we have further discussion about our Compatibility issues, I'd like

Re: [classlib]bug-to-bug compatibility j.u.Formatter

2006-07-25 Thread Richard Liang
Anton Luht wrote: Hello, And there are places RI behaves irrational and not compatible with RI. You mean RI behaves not compatible with spec? :) Kidding :-) I think it's yes: "And there are places RI behaves irrational and not compatible with Spec." Best regards, Richard -- Richard Lian

Re: [classlib]bug-to-bug compatibility j.u.Formatter

2006-07-25 Thread Richard Liang
Spark Shen wrote: Richard Liang 写道: Hello All, As we have further discussion about our Compatibility issues, I'd like to summarize this particular problems and ask for comments. Thanks a lot. If we pass a null to j.u.Formatter.Formatter(Appendable a), when we try to get the destination o

Re: [classlib]bug-to-bug compatibility j.u.Formatter

2006-07-25 Thread Anton Luht
Hello, And there are places RI behaves irrational and not compatible with RI. You mean RI behaves not compatible with spec? :) -- Regards, Anton Luht, Intel Middleware Products Division - Terms of use : http://incubator.apac

Re: [classlib]bug-to-bug compatibility j.u.Formatter

2006-07-25 Thread Spark Shen
Richard Liang 写道: Hello All, As we have further discussion about our Compatibility issues, I'd like to summarize this particular problems and ask for comments. Thanks a lot. If we pass a null to j.u.Formatter.Formatter(Appendable a), when we try to get the destination of the formatter's outp

Re: [classlib]bug-to-bug compatibility j.u.Formatter

2006-07-25 Thread Richard Liang
Hello All, As we have further discussion about our Compatibility issues, I'd like to summarize this particular problems and ask for comments. Thanks a lot. If we pass a null to j.u.Formatter.Formatter(Appendable a), when we try to get the destination of the formatter's output by calling form