Design philosophies like this should be documented in the project - that
way there is no need to hash out the correct approach for every line of
code.
Everyone has different design philosophies, and in some cases there is
no "right" or "wrong" philosophy. [In this thread, two fail-slow designs
that provide default values, and one fail-fast design that throws an
exception.] So, it helps if a project can state clearly its fundamental
design philosophy. Some users might disagree with it, but at least it
makes code maintenance and new development easier.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 3/17/2014 11:42 AM, Gary Gregory wrote:
I re-implemented the simplest behavior (back to what we had before): null
-> IAE.
Gary
On Mon, Mar 17, 2014 at 2:31 PM, Emmanuel Bourg <ebo...@apache.org> wrote:
Le 17/03/2014 19:21, Gary Gregory a écrit :
OK, then we are back to null -> exception. Check?
I'd say default to the system encoding, like most methods of this kind.
Emmanuel Bourg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
