Re: Re[4]: Barracuda: Patch for IterativeListModel
"Diez B. Roggisch" <[email protected]>
| Newsgroups | gmane.comp.java.enhydra.barracuda.general |
|---|---|
| Message-ID | <[email protected]> |
> DBR> Thats not true - the above construct will create an anonymous class, > which can DBR> implement interfaces, thus abstract methods are no problem. > > Maybe I'm just showing my naivete, but if a class is made abstract, > you can't instantiate it by calling "new" on it. I would think that > by calling it AbstractIterativeListModel we'd then change the class > to "public abstract class", right? Please explain what you mean. Take a close look at the construct: I implement the getItem-method in the block of curly braces rigth after the invocation of "new IterativeListModel". This is the syntax for an anonymous inner class. Instead I could have written a named inner class, but as I'm not interested in the class having a name - why should I? Try it for yourself, e.g. with the Runnable interface. > DBR> Regarding the postIterate method: I ususally null not needed iterators > and DBR> stuff, this one must have slipped me. > > Cool. Are you going to make those modifications? Sometime after the move > to the new server we'll be making a new release and it would probably be > good to get this stuff moved into the core before that. Otherwise, it will > have to wait for a later release. I can make the changes so that the iterator is nulled. However, as I'm not sure where you guys want to place things finally in the refactoring process, I think that should be done by one of you. Diez _______________________________________________ Barracuda mailing list [email protected] http://www.enhydra.org/mailman/listinfo.cgi/barracuda FAQ - http://www.jguru.com/faq/Barracuda