Web Images Videos Maps News Shopping Gmail more »
Recently Visited Groups | Help | Sign in
Google Groups Home
best practices for exception hierarchies?
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Joshua Haberman  
View profile  
 More options Mar 19 2006, 1:11 pm
Newsgroups: comp.lang.ruby
From: Joshua Haberman <jos...@reverberate.org>
Date: Mon, 20 Mar 2006 03:11:41 +0900
Local: Sun, Mar 19 2006 1:11 pm
Subject: best practices for exception hierarchies?
What are best-practices for exception hierarchies?

Should my exceptions derive from Exception, or StandardError, or  
RuntimeError?

Should my exceptions be called FooException or FooError?  Does Ruby  
give a specific meaning to the difference between an "Error" and an  
"Exception?"

Josh


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google