[#63592] [ruby-trunk - Bug #10009] IO operation is 10x slower in multi-thread environment — normalperson@...
Issue #10009 has been updated by Eric Wong.
3 messages
2014/07/08
[#63682] [ruby-trunk - Feature #10030] [PATCH] reduce rb_iseq_struct to 296 bytes — ko1@...
Issue #10030 has been updated by Koichi Sasada.
3 messages
2014/07/13
[#63703] [ruby-trunk - Feature #10030] [PATCH] reduce rb_iseq_struct to 296 bytes — ko1@...
Issue #10030 has been updated by Koichi Sasada.
3 messages
2014/07/14
[#63743] [ruby-trunk - Bug #10037] Since r46798 on Solaris, "[BUG] rb_vm_get_cref: unreachable" during make — ngotogenome@...
Issue #10037 has been updated by Naohisa Goto.
3 messages
2014/07/15
[#64136] Ruby 2.1.2 (and 2.1.1 and probably others) assumes a libffi with 3 version numbers in extconf.rb — "Jeffrey 'jf' Lim" <jfs.world@...>
As per subject.
4 messages
2014/07/31
[#64138] Re: Ruby 2.1.2 (and 2.1.1 and probably others) assumes a libffi with 3 version numbers in extconf.rb
— "Jeffrey 'jf' Lim" <jfs.world@...>
2014/07/31
On Thu, Jul 31, 2014 at 6:03 PM, Jeffrey 'jf' Lim <[email protected]>
[ruby-core:63615] [ruby-trunk - Bug #10021] OptParse does not handle missing arguments bracketed by valid option switches
From:
byrnejb@...
Date:
2014-07-09 20:38:52 UTC
List:
ruby-core #63615
Issue #10021 has been updated by James Byrne.
When I try this:
`--re-run x -r --rerun y -- file`
Then I see this
`:in `eval': Only one output filename is permitted (RuntimeError)
`
From which I infer that -r has 'eaten' --rerun as its argument and is treating y as the file name (args[0])
But if I do this:
`--re-run x -re-run --rerun y -- file
`
Then the program runs. I exposed the structures with a debug routine and this is what they show:
`Options before parsing with --debug
Number of arguments passed: 8
Arguments passed are:
---
- "--debug"
- "--re-run"
- x
- "-re-run"
- "--rerun"
- y
- "--"
- file
Argument object contains:
["--debug", "--re-run", "x", "-re-run", "--rerun", "y", "--", "file"]`
----------------------------------------
Bug #10021: OptParse does not handle missing arguments bracketed by valid option switches
https://bugs.ruby-lang.org/issues/10021#change-47669
* Author: James Byrne
* Status: Open
* Priority: Normal
* Assignee:
* Category: core
* Target version:
* ruby -v: Ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux-gnu]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
OS=CentOS-6.5 x86_64
Ruby=2.1.2p95
I have this in an optparse structure:
# Create parser
opts = OptionParser.new do |opts|
opts.banner = <<-BANNER
. . .
opts.on("-r", "--rerun=DATEorTRANSACTION", "--re-run=DATEorTRANSACTION",
"Re-run extract for specific date (yyyymmdd)",
" or transaction number (SSSSSNNNNNNNNC).",
" Multiple specifications are ORed for selections.",
" All billable transactions are selectable",
" whether previously billed or not.",
" Sets and enforces --no-update" ) do |rr|
options.rerun << rr
options.update = false
end
. . .
If I run a program incorporating this option class so:
--re-run x --rerun y -r
Then I see this:
missing argument: -r
However, if I do this:
--re-run x --rerun y -r --debug
or this
--re-run x -r --rerun y
Then the program runs and does not report the missing argument.
Is this the intended behaviour? It does not seem correct to me.
--
https://bugs.ruby-lang.org/