From: James Coglan <jcoglan@...>
Date: 2008-07-12T01:59:56+09:00
Subject: Re: Piping data in on the command line

------=_Part_45030_23614694.1215795844895
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

2008/7/11 Sandor Sz=FCcs <sandor.szuecs@fu-berlin.de>:

>
> On 09.07.2008, at 14:34, Martin Boese wrote:
>
>  Just read the IO $stdin, like:
>>
>> $stdin.each { |line| puts "Found: #{line}" }
>>
>> The < "operator" is a shell feature that will pass the content of a file
>> to
>> the programs standard input (stdin).
>>
>
>
> Maybe that's more readable, but my point wasn't the shell feature < .
> cat.rb has one line:
> puts *ARGF



Thank you both. If anyone is the least bit interested I'm writing myself ye=
t
another commandline option parser:

http://github.com/jcoglan/oyster

It's inspired by trollop, but it has some more option types and is more
easily extensible, automates a few extra things (like recognizing
--no-verbose if you've got a --verbose option for example) and it generates
slightly nicer (more man-page-like) help text.

------=_Part_45030_23614694.1215795844895--