AbstractListModel.fireContentsChanged() says
that index0 need not be <= index1.
Yet, ListDataEvent says that index0 is "lower"
index value.

I recommend that AbstractListModel.fireContentsChanged()
docs be changed to say index0 must be <= index1.
(which is always the case now anyways).

If that's no good, then add the code to swap index0 and
index1 if necessary.

Under no circumstances should ListDataEvent.getIndex0() be
changed to be possibly bigger than getIndex1().  The reason
is that you have to include some yucky code to handle the 
possibility.  The second reason is that most people will
not write the appropriate code anyways (since it will
work fine presently).  And so if in the future you ever
want to make index0 bigger than index1, you'll break everyone's
code. In  xxxxx  words, you won't be able to do it anyways.
So you might as well be clear here.

Besides, the restriction that index0 <= index1 is not onerous
but handling the case is onerous.

cheers,
pat
(Review ID: 48508)
======================================================================

int i = evt.getIndex0();
int j = evt.getIndex1();
if (i > j) {
  int t = i;
  i = j;
  j = t;
}
for (i=0; i<=j; i++) {
  evt.getElementAt(i);
}
======================================================================

I agree, AbsractListModel should swap the indexs as necessary so that ListDataEvent is created correctly.
 xxxxx@xxxxx  1999-09-22

Actually, ListDataEvent should probably do this, that way everyone will pick it up.
 xxxxx@xxxxx  2001-10-22