From: Stu Glaser <stuglaser@...>
Date: 2005-11-13T00:56:34+09:00
Subject: Re: programming best practices

I feel that if a function fails so badly that the "do_stuff" section of 
your code will fail, then you should really throw an exception.  This 
way if someone forgets to check the return value, they will not become 
confused as to why later code does not work.  Throwing an exception 
forces downstream programmers to use your code properly.

Especially if you plan to "complain" if login fails.

See the "Samurai Principle"
http://c2.com/cgi/wiki?SamuraiPrinciple

Return victorious or not at all!
-Stu

swille wrote:
> I have a couple of standard programming questions.  The first is that
> I often like to return true or false in a method when no other return
> value is really needed.  Is that bad form?  I was talking to someone
> the other day who said said something that made me think that maybe it
> was.  For example: