Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

FIOC exception classes

Name: Anonymous 2012-05-30 5:35

Which approach do you prefer:

1. Create new exceptions for each class of error in your libs.

2. Just use stuff from the exceptions module most of the time and create new exceptions when using a standard one is really inappropriate.

My colleagues strongly prefer #1, and go around making dozens of FilePermissionsError or ValueErrorBecauseFuckYou.  They are also OOP and Patterns nuts.  I am not a very happy man because I have to import their horde of bullshit exceptions into my modules instead of just using standard classes.

Name: Anonymous 2012-06-22 15:41

Ruby user here, #2 is preferred. Because half the shit you need typically can be expressed as TypeError, ArgumentError, etc... anything special can be given an additional Error message to separate it out, so you can just

rescue StandardError => err
    if err.message.include? "Fuck You" then
        # Handle fuck you exception
    else
        # Handle some other exception
    end
end

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List