I feel so silly asking, but do you mean along the lines of this?
File.open("nul", "w")
No, wait. That’d just make a file called “nul”, wouldn’t it? What
am I missing
here?
No more so that File.open(“/dev/null”, “w”) would create a file named
/dev/null in unix, no.
That makes sense. I was confused, though, because there actually is a
file “/dev/null” on my UNIX box, but I didn’t see a file “nul” on the
Windows machine.
I think NUL is perhaps better written as NUL: (i.e.,
it’s a device like CON or whatever all the others
are).
Hal
···
----- Original Message -----
From: “Brian Wisti” brian@coolnamehere.com
To: “ruby-talk ML” ruby-talk@ruby-lang.org
Sent: Tuesday, November 19, 2002 10:18 AM
Subject: Re: Windows bitbucket equivalent?
I feel so silly asking, but do you mean along the lines of this?
File.open("nul", "w")
No, wait. That’d just make a file called “nul”, wouldn’t it? What
am I missing
here?
No more so that File.open(“/dev/null”, “w”) would create a file named
/dev/null in unix, no.
That makes sense. I was confused, though, because there actually is a
file “/dev/null” on my UNIX box, but I didn’t see a file “nul” on the
Windows machine.
No more so that File.open(“/dev/null”, “w”) would create a file
named
/dev/null in unix, no.
That makes sense. I was confused, though, because there actually
is a
file “/dev/null” on my UNIX box, but I didn’t see a file “nul” on
the
Windows machine.
Yeah, like so many other M$ “features”, they probably didn’t want to
confuse the masses with sillyness like actually HAVING the
file/device there rather than making it “magic”.