On Sun, Apr 4, 2010 at 1:43 PM, Happy-melon <happy-melon(a)live.com> wrote:
As Roan says, a Message object essentially deprecates
the (IMO pig-ugly)
Status class, which is used erratically throughout the codebase as
essentially a way to bundle up a message key, some parameters, and a success
flag without converting to String too soon. Status has always struck me as
an unpleasant implementation: processes should throw exceptions on fatal
errors, return messages on non-catastrophic problems, and bool true on
success.
As opposed to returning a single class which can handle errors, warnings
and OK statuses just fine? I really don't know why people don't like the
Status class, I'm trying to use it *more* in the new-installer, rather than
returning weird mixtures of booleans, strings and exceptions.
-Chad