From: Phlip <phlip_cpp@...>
Date: 2001-12-17T10:36:12+09:00
Subject: [ruby-talk:28723] Re: stderr from external process?

MikkelFJ sez:

> The first tiny step in this respect is to call an external compiler -
> and to trap error messages.
> These error messages frequently arrive at stderr. How do you get to
> those?

A quick grep open3 `locate .rb` reveals this:

/usr/lib/ruby/1.6/open3.rb:#    in, out, err = Open3.popen3('nroff -man')

Appears that 'popen3' runs a command with 3 pipes on it...

> Longer term: I really hate the build tools around. "Ant" is an attempt
> to make something better in Java.
> I figure Ruby would be the perfect language for a build tool. You could
> also write custom classes for scanning dependencies on custom file
> types.
> And perhaps use the Workflow module I recently saw on RAA to manage
> distributed builds.

Try Jam.

-- 
  Phlip                          phlip_cpp@yahoo.com
           http://flea.sourceforge.net
  --  "Probably one of the toughest times in anyone's life is when
       you have to kill someone you love because they'r the Devil"
                                     --Emo Phillips  --