On 4/9/97 at 8:15 PM, Harry Lewis said ...
There was quite a bit of discussion upon adding this to the jmGeneral table
last week in Austin. After reviewing back here, we still don't see how this
value serves it's purpose. Does someone have a write-up of exactly what this
object is supposed to do?
We feel another object is also required... basically something like
jmGeneralHighestActiveIndex otherwise it is very difficult to avoid walking the
whole table.
We feel that these should be named
jmGeneralOldestActiveIndex
jmGeneralNewestActiveIndex
this helps get around the wrap problem.
Using these two objects, an application should be about to determine where to
start in the table (Oldest) and where to stop (Newest) and should also know
there will be a wrap if Newest is a smaller number than oldest.
SWR>> I think you are right. jmGeneralLeastActiveIndex tells where to start
scanning the table, but not where to stop. I am in favor of this change, and
I think the names Oldest and Newest are an improvement.
Stuart