mjijackson/citrus — comment on commit 2a79ad93874b687736edf71e4948280dd6d91aee
File: lib/citrus.rb line 403
By blambeau:

Well, I know at least one gem (epath) that provide a Path implementation, far better than Pathname, and which will not be usable here. Checking for respond_to?(:to_path) is standard in the ruby 1.9.x branch.

Also, I'm not sure that raising a Citrus::Error is actually a good idea if something goes wrong with the file. I would say that the path must exit and be readable as a precondition and that a IOError may occur otherwise.

What do you think?