I'm not sure I understand your question.... you mean why would one want to stick to public APIs?
No, that's not what I meant. I definitely agree that we should stick to publich APIs as much as we can.
If it can be done in a separate class, using public APIs (or at least with a minimum of protected access), without a loss in performance, then that's the way to go IMO.
This is exactly what I'm asking. Can it be done using public APIs without a loss in performance or functionality? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
