On 22 March 2012 12:34, Matthew Adams <matt...@matthewadams.me> wrote:
> On Thu, Mar 22, 2012 at 6:06 AM, Stephen Colebourne
> <scolebou...@joda.org> wrote:
>>> 3/ PeriodPrinter.printTo, DateTimePrinter.printTo
>>>
>>> Both interfaces define printTo methods that use a StringBuffer as argument.
>>> It is be better to use an AbstractStringBuilder now instead.
>>
>> That would be backwards incompatible.
>
> First, I'd recommend the use of interface CharSequence instead.
>
> Second, I don't see how that would that be backward incompatible.
> StringBuilder & StringBuffer both implement CharSequence.  By changing
> the signatures to take a CharSequence, you'd be effectively relaxing
> the restriction of using StringBuilder and allowing a larger range of
> types.  Can you please elaborate?

Binary compatibiilty. The change of signature would be source
compatible, but not binary compatible. Existing code compiled against
the old API would fail if it was changed. Adding a second parallel
method (which would be compatible) is just bloat.

Stephen

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Joda-interest mailing list
Joda-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/joda-interest

Reply via email to