Just ease of use really... I have our MultiSearcher reload transparently and this case I can verify that I'm using the right array of searchers not one that's already been reloaded behind me.
No question that it'd be unwise to do. We could say the same argument for making everything public access as well and say it'd be stupid to override this method, but we made it public anyway. I'd rather opt on the side of safety.
Besides, you haven't provided a use case for why you need to get the searchers back from a MultiSearcher :)
I can add some code to preserve the original searcher array but it's a pain.
Kevin
--
Please reply using PGP.
http://peerfear.org/pubkey.asc NewsMonster - http://www.newsmonster.org/
Kevin A. Burton, Location - San Francisco, CA, Cell - 415.595.9965
AIM/YIM - sfburtonator, Web - http://peerfear.org/
GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412
IRC - freenode.net #infoanarchy | #p2p-hackers | #newsmonster
signature.asc
Description: OpenPGP digital signature
