gem.sh

Name

sysexits

Version

1.2.0

Platform

ruby

Authors

Michael Granger

Bindir

bin

Cert chain

Date

2014-08-08 00:00:00 UTC

Dependencies

hoe-mercurial (~> 1.4.0, development)
hoe-highline (~> 0.1.0, development)
rdoc (~> 4.0, development)
rspec (~> 2.11, development)
simplecov (~> 0.6, development)
hoe (~> 3.9, development)

Description

Have you ever wanted to call <code>exit()</code> with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then. Anyway, I was reading manpages late one evening before retiring to bed in my palatial estate in rural Oregon, and I stumbled across <code>sysexits(3)</code>. Much to my chagrin, I couldn't find a +sysexits+ for Ruby! Well, for the other 2 people that actually care about <code>style(9)</code> as it applies to Ruby code, now there is one! Sysexits is a *completely* *awesome* collection of human-readable constants for the standard (BSDish) exit codes, used as arguments to +exit+ to indicate a specific error condition to the parent process. It's so fantastically fabulous that you'll want to fork it right away to avoid being thought of as that guy that's still using Webrick for his blog. I mean, <code>exit(1)</code> is so passé! This is like the 14-point font of Systems Programming. Like the C header file from which this was derived (I mean forked, naturally), error numbers begin at <code>Sysexits::EX__BASE</code> (which is way more cool than plain old +64+) to reduce the possibility of clashing with other exit statuses that other programs may already return. The codes are available in two forms: as constants which can be imported into your own namespace via <code>include Sysexits</code>, or as <code>Sysexits::STATUS_CODES</code>, a Hash keyed by Symbols derived from the constant names. Allow me to demonstrate. First, the old way: exit( 69 ) Whaaa...? Is that a euphemism? What's going on? See how unattractive and... well, 1970 that is? We're not changing vaccuum tubes here, people, we're <em>building a totally-awesome future in the Cloud™!</em> include Sysexits exit EX_UNAVAILABLE Okay, at least this is readable to people who have used <code>fork()</code> more than twice, but you could do so much better! include Sysexits exit :unavailable Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in which variable++ is possible! Well, okay, it's not quite that cool. But it does look more Rubyish. And no monkeys were patched in the filming of this episode! All the simpletons still exiting with icky _numbers_ can still continue blithely along, none the wiser.

Email

ged@FaerieMUD.org

Extra rdoc files

History.rdoc
Manifest.txt
README.rdoc

Files

.gemtest
ChangeLog
History.rdoc
LICENSE
Manifest.txt
README.rdoc
Rakefile
lib/sysexits.rb
spec/sysexits_spec.rb

Homepage

https://bitbucket.org/ged/sysexits

Licenses

BSD

Rdoc options

-f
fivefish
-t
Sysexits

Require paths

lib

Required ruby version

>= 1.8.7

Required rubygems version

>= 0

Rubyforge project

sysexits

Rubygems version

2.2.2

Specification version

4

Summary

Have you ever wanted to call <code>exit()</code> with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then

Original platform

ruby

New platform

ruby

Modules

Metadata

Top-Level Modules