Is there anybody on this list with:
ruby 1.8.3 or 1.8.4 and
rio-0.3.4
who can run this:
require 'rubygems'
require 'rio'
p rio(??).mkdir.path
without getting an error message?
···
--
Wybo
Is there anybody on this list with:
ruby 1.8.3 or 1.8.4 and
rio-0.3.4
who can run this:
require 'rubygems'
require 'rio'
p rio(??).mkdir.path
without getting an error message?
--
Wybo
no problemos.
> riotest.rb
"/cygdrive/c/DOCUME~1/LOUVAN~1/LOCALS~1/Temp/rio17216.0"
> ruby -v
ruby 1.8.4 (2005-12-26) [i386-cygwin]
> gem list --local | grep -i rio
rio (0.3.4)
Rio - Ruby I/O Comfort Class
Wybo Dekker wrote:
Is there anybody on this list with:
ruby 1.8.3 or 1.8.4 and rio-0.3.4
who can run this:
require 'rubygems'
require 'rio'
p rio(??).mkdir.pathwithout getting an error message?
no problemos.
> riotest.rb
"/cygdrive/c/DOCUME~1/LOUVAN~1/LOCALS~1/Temp/rio17216.0"
> ruby -v
ruby 1.8.4 (2005-12-26) [i386-cygwin]
> gem list --local | grep -i rio
rio (0.3.4)
Rio - Ruby I/O Comfort Class
Thanks, good to have finally a test.
You have a windows system, apparently?
So my problem must be a linux-problem, a friend, also under linux, has the
same problem:
/usr/local/lib/ruby/gems/1.8/gems/rio-0.3.4/lib/rio/ops/dir.rb:77:
uninitialized constant RIO::Ops::FileOrDir::ExistOrNot (NameError)
On Thu, 5 Jan 2006, Lou Vanek wrote:
Wybo Dekker wrote:
> Is there anybody on this list with:
>
> ruby 1.8.3 or 1.8.4 and rio-0.3.4
> who can run this:
>
> require 'rubygems'
> require 'rio'
> p rio(??).mkdir.path
>
> without getting an error message?
--
Wybo