On 9/22/2011 7:03 PM, Jörn Kottmann wrote: > On 9/23/11 12:52 AM, James Kosin wrote: >> Yes, that makes better sense... unfortunately, if the user uses the >> getStart() and getEnd() methods for a Span and tried to use those >> numbers it may add even more confusion; since the getEnd() returns one >> past the last index in the span. >> Maybe we should refactor the Span class to clarify the proper usage... >> or provide better documentation. > > As far as I know it is quite common to define a range as we did. There > are a couple > of other APIs I know of which do it the same way. > > +1 to improve the documentation. > > Jörn > Would it be okay to define the toString() method to return the mathmatical representation of the actual span? example output: [0..7) To show the span contains 0 as one of the endpoints and does not include 7.
James
