Hello. Le jeu. 29 juin 2023 à 14:44, Gary Gregory <garydgreg...@gmail.com> a écrit : > [...] > > Java makes a clear distinction between checked and unchecked > exceptions. As a mid-level API, I do not feel Pool should take a > design POV that is different from Java's intended pattern regarding > exceptions.
I agree with the second part assuming the *current* Java best practices, not because of old APIs that are here to stay only because of infinite backwards compatibility, and not because they are deemed perfect. I don't see any relationship between "mid-level API" and "checked exceptions". Any reference (of modern code) for it? > > The 3.0 API should use checked exceptions -1 > and the implementation wrap > unchecked runtime exceptions. This will allow call sites to either > propagate or catch the one exception. The one "PoolException" need not be checked, to the same effect from an application developer POV. Gilles > > [...] --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
