>>>>> "Roman" == Roman Kennke <[EMAIL PROTECTED]> writes:
>> This means multiple allocations per layout. Roman> I could easily optimize this. I would have to return an implementation Roman> of Collection (or List, for correctness of semantics) that wraps the Roman> Component[] returned by getComponents() and provides an Iterator over Roman> this. This could still mean 2 allocations per layout (one for the List, Roman> one for the collection), but both could probably be cached for later Roman> use. Roman> Do you think this is preferable? Or should the LayoutManagers sort this Roman> out on themselves? I'm not at all sure that it even matters whether we do this. But if it does matter, I would guess that adding 'if (! visible)' to the layout managers would be the least heavy. Tom _______________________________________________ Classpath-patches mailing list [email protected] http://lists.gnu.org/mailman/listinfo/classpath-patches
