On Mon, Oct 7, 2013 at 3:17 PM, Jeroen De Dauw <jeroended...@gmail.com>wrote:
> The Status object is many ways is a fancy error code. It causes the same > issues as returning error codes. It differs with the proposal in that the > Status object deals with error cases, while the proposal does not. > The real question is why can't the Status object just be supplemented to support this functionality. Like Brad said, it's really not a good idea to introduce yet another method of error handling. Also, the Status class does achieve more than just being a fancy error code. It allows clear distinction between return values and error values, which is something not always guaranteed by the "return null/false" strategy. *-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l