$stdout vs STDOUT

drbrain@segment7.net (Eric Hodel) — Thu, 17 Aug 2006 09:47:00 -0700

You may have noticed me using both $stdout and STDOUT in my last post and been puzzled by how I could use both.

When Ruby starts up the process’ standard output file descriptor is stored in both the constant STDOUT and the global variable $stdout. STDOUT holds the process’ original stdout while $stdout is reassignable. Kernel#puts and friends use $stdout to write their output, not STDOUT.

To be most-friendly, when you want to redirect stdout you should assign to $stdout instead of fiddling with STDOUT. When outputting to an explicit file descriptor, use $stdout or $stderr instead of STDOUT or STDERR.

STDOUT can only be changed by calling IO#reopen, but you can assign any object that responds to #write to $stdout, which is what made my ThreadOut hack work.

"$stdout vs STDOUT" by Daniel Berger

Thu, 17 Aug 2006 12:14:01 -0700

Nice, thanks.

Segment7: $stdout vs STDOUT

$stdout vs STDOUT

"$stdout vs STDOUT" by Daniel Berger