[#8787] Literal inconsistency — Calamitas <calamitates@...>
Hi,
Calamitas <calamitates@gmail.com> writes:
On 9/4/06, Christian Neukirchen <chneukirchen@gmail.com> wrote:
[#8794] bignums — Ondrej Bilka <neleai@...>
I want ask how look integration of faster bignums.
[#8798] okay, threading & sandbox r70 -- the latest patch — why the lucky stiff <ruby-core@...>
We have previously talked about getting the sandbox to obey thread switching on
Hi,
[#8802] WEBrick::Cookie support for multiple cookies per set-cookie — Aaron Patterson <aaron_patterson@...>
WEBrick's cookie class has a method for parsing Set-Cookie headers, but
[#8813] ruby-1.8.5 loads fox16.so more than once — <noreply@...>
Bugs item #5701, was opened at 2006-09-08 20:59
[#8815] Segfault in libc strlen, via rb_str_new2 — "Sean E. Russell" <ser@...>
Howdy,
On Sep 8, 2006, at 10:10 PM, Sean E. Russell wrote:
On Saturday 09 September 2006 01:42, Eric Hodel wrote:
On Sep 9, 2006, at 7:16 PM, Sean E. Russell wrote:
On Sunday 10 September 2006 22:57, Eric Hodel wrote:
[#8826] OptionParser < Hash — "greg weber" <eegreg@...>
Hi,
[#8828] REXML fails to parse UTF-16 XML. — <noreply@...>
Bugs item #5711, was opened at 2006-09-11 01:25
Hi,
[#8861] new changes in strings+symbols — Mathieu Bouchard <matju@...>
On Wed, 13 Sep 2006, matz wrote:
[#8864] documentation of ruby internals — Deni George <denigeorge@...>
Hello
On Thursday 14 September 2006 11:30, Deni George wrote:
[#8885] numeric.c fails to build on 64-bit platforms (Fedora Core 5 x86_64 gcc 4.1.1) — <noreply@...>
Patches item #5774, was opened at 2006-09-16 12:19
Hi,
[#8897] Ruby's 'etc' module cannot handle the UID of OS X 'nobody' properly — <noreply@...>
Bugs item #5822, was opened at 2006-09-20 11:13
Hi,
[#8904] patch bignums — Ondrej Bilka <neleai@...>
I am so far with implementing faster bignums:
[#8920] rdoc capture output (help message) — "greg weber" <eegreg@...>
Hi,
The simplest command line would be
greg weber wrote:
It looks like you could seperate this out into a rake task, but then
On Sep 29, 2006, at 5:52 AM, greg weber wrote:
[#8929] Re: RDoc patch, possible bug in socket.c for TCPSocket.new — gwtmp01@...
[#8948] socket (and many others) not building on osx? — Ryan Davis <ryand-ruby@...>
I'm stumped. A brand new clean build doesn't build socket.
[#8954] The %? .. ? Operator — James Edward Gray II <james@...>
I'm needing to know the full list of characters that can (or cannot)
On Sep 29, 2006, at 9:56 AM, James Edward Gray II wrote:
Re: [PATCH] OptionParser < Hash
> OptionParser's methods are partioned to 2 kinds. Methods to register
> the options, and methods to parse the command line. The former does
> modify the receiver, but the latter never. I don't plan to change
> this concept.
>
This is my first patch submission, so I hope I am not being rude, and
I appreciate the your response and the work that everyone here does.
I think it is important to question anything that conflict with your
ideas about the architecture. However, a change that conflicts with
an architectural idea does not in itself mean the change is bad. It
could mean that the architectural idea is overly rigid.
My patch does seem kind of hackish. Perhaps you would be more
comfortable with adding a state variable, @auto_options = {}, that
would implement this option hash instead of using self. I don't see
any downside to this- users are free to ignore it. Those who use it
will avoid creating a boilerplate outer class and boilerplate variable
settings, making them more productive and happier :)
>
> @text = true
> @eol = nil
> OptionParser.new do |q|
> ot = q.def_option("--text") {@text = true}
> ob = q.def_option("--binary") {@text = false}
> oe = q.def_option("--eol=EOL", %w[UNIX DOS OS9]) {|eol| @eol = eol}
> q.exclusive(ob, oe) # <=== eol and binary are exclusive
> q.requires(oe, ot) # <=== eol requires text
> end
>
I do not see the exclusive and requires methods. What version do I
need for these to work?
One more comment- I think the OptionParser library would do well to
make some of its public methods private or combine them. The
multitude of public methods maked it harder to figure out which
methods should be used. For example, it would perhaps be better to
eliminate on and just use define. It would also be good to make order
and permute private, but callable from parse by setting keyword
arguments.
One more question- is there a way to collect the help output message
from OptionParser with RDoc?
Thank you
Greg Weber