dirge 0.0.3 → 0.0.4

data/README.rdoc

@@ -4,7 +4,7 @@
 
   require 'dirge'
   require_relative '../to_my_file'
-  
+
 Or, the much simpler notation
 
   require ~'../to_my_file'
@@ -24,3 +24,19 @@ Again, this could be
 All of this is powered by the new function:
   
   __DIR__
+  
+which takes a single line off of <tt>Kernel.caller</tt> and give you back the relative path. Calling __DIR__(caller.first) for instance, will give you the relative path to whoever called you.
+
+There is also a more explicit, and probably, more readable version.
+
+  File.relative(path)
+
+This will convert your path into a relative directory from wherever you are.
+
+  require_relative 'to/my/file'
+  
+and 
+
+  require File.relative('to/my/file')
+  
+should be identical.

data/VERSION

@@ -1 +1 @@
-0.0.3
+0.0.4

data/lib/dirge.rb

@@ -31,4 +31,10 @@ class String
       File.expand_path(File.join(__DIR_REL__(caller.first), self))
     end
   end
+end
+
+class File
+  def self.relative(path)
+    File.expand_path(File.join(__DIR_REL__(caller.first), path))
+  end
 end

data/spec/dirge_spec.rb

@@ -1,8 +1,12 @@
 describe 'Dirge' do
-  it "should resolve a path" do
+  it "should resolve a path through String#~" do
     (~'test:2test/test').should == File.expand_path(File.join(File.dirname(__FILE__), 'test:2test', 'test'))
   end
   
+  it "should resolve a path through File#relative" do
+    File.relative('test:2test/test').should == File.expand_path(File.join(File.dirname(__FILE__), 'test:2test', 'test'))
+  end
+  
   it 'should require a relative path' do
     proc {
       require_relative 'test:2test/test'

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: dirge
 version: !ruby/object:Gem::Version 
-  version: 0.0.3
+  version: 0.0.4
 platform: ruby
 authors: 
 - Joshua Hull
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2009-11-21 00:00:00 -08:00
+date: 2010-01-24 00:00:00 -05:00
 default_executable: 
 dependencies: []