Josh McDonald wrote:
> It's not the idea we're objecting to so much as the suggested
> implementation.
>
> But the problem is no matter how nice your implementation is, you've
> still got to maintain a list of "allowed" classes, which is fine for
> you. Unfortunately when you've moved interstate, and your replacement's
> replacement adds a class to the package full of "allowed" classes, and
> it takes him a week to figure out what the bejesus you did.
>
When Dark Magic is used it must be documented, regardless of
emotionally-charged implementation choices. A very minor discussion in
the package or class docs should be enough to send Hapless Maintainer to
the right place ("Would you like to biggie-size that?")...
This seems like something that could/should be handled AOPly anyway, but
as I said before, we did the exact same thing once before, and it was
worse because the "stack trace as an array" method wasn't invented yet.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
