I agree, it is not an "error", and so should not be an exception.
Jesse Phillips wrote:
Is there a reason to make them exceptions? The whole point is to tell
you if it is or is not a function. I would not consider it an error
code more a "reason code" (why it wasn't an email address).
On Fri, Mar 4, 2011 at 2:12 PM, Jacob Carlborg <[email protected]> wrote:
I've ported the isemail module from PHP to D and I'm now working on adding exceptions instead of
error codes. The PHP function takes an error level parameter indicating what kind of error level
you want. You can pass in a warning and error level and possible others as well. You can also turn
the error handling completely off. If the error handling is turned off the function will only
return "true" or "false" indicating if the email address is valid or not.
If the error handling is on the function will return 0 if the email address is
valid or otherwise an error code indicating what the error was.
The question I now has is: should we keep these different error levels or
should we just have a parameter indicating if the error handling is on or off?
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
