[#11073] segfault printing instruction sequence for iterator — <noreply@...>
Bugs item #10527, was opened at 2007-05-02 14:42
Hi,
On Thu, May 10, 2007 at 04:51:18PM +0900, Nobuyoshi Nakada wrote:
Hi,
Hi,
This seems to make valgrind much happier.
On Thu, May 17, 2007 at 11:14:35PM +0900, Paul Brannan wrote:
Hi,
Now 'a' shows up twice in the local table:
Hi,
[#11082] Understanding code: Kernel#require and blocks. — Hugh Sasse <hgs@...>
I'm trying to debug a Rails application which complains about an
On 5/4/07, Hugh Sasse <hgs@dmu.ac.uk> wrote:
On Fri, 4 May 2007, George wrote:
On Fri, May 04, 2007 at 06:18:19PM +0900, Hugh Sasse wrote:
[#11108] pattern for implementation-private constants? — David Flanagan <david@...>
Hi,
I believe there isn't a way, but I don't think it's really necessary. Just
[#11127] Bugs that can be closed — "Jano Svitok" <jan.svitok@...>
I propose closing these bugs as invalid:
[#11145] Rational comparison to 0 fails when denominator is != 1 — <noreply@...>
Bugs item #10739, was opened at 2007-05-10 22:06
Hi,
[#11169] Allow back reference with nest level in Oniguruma for Ruby again — =?ISO-8859-15?Q?Wolfgang_N=E1dasi-Donner?= <wonado@...>
Remark: I posted this text in comp.lang.ruby first, but Matz told me,
Does it make sense or is it required to write this as a RCR?
[#11176] FileUtils.rm_rf misfeature? — johan556@...
Hi!
[#11210] Pathname ascend and descend inclusive parameter — TRANS <transfire@...>
I would like to suggest that Pathname#ascend and Pathname#descend
[#11234] Planning to release 1.8.6 errata — Urabe Shyouhei <shyouhei@...>
Hi all.
On 25/05/07, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:
[#11252] Init_stack and ruby_init_stack fail to reinit stack (threads problem?) — <noreply@...>
Bugs item #11134, was opened at 2007-05-25 12:14
Hi,
Nobuyoshi Nakada wrote:
[#11255] ruby_1_8_6 build problem (make install-doc) — johan556@...
Hi!
[#11271] providing better support through rubyforge tracker categories — Ryan Davis <ryand-ruby@...>
I'm going to make more categories for the trackers (bugs and patches)
[#11367] BUG: next in lambda: 1.8.6 differs from 1.8.4 and 1.9.0 — David Flanagan <david@...>
A toplevel next statement in a lambda does not return a value in 1.8.6,
[#11368] $2000 USD Reward for help fixing Segmentation Fault in GC — Brent Roman <brent@...>
Hi Brent,
Net::Telnet and EOF
I've noticed what appears to be an inconsistency in the behaviour of
Net::Telnet's waitfor() method.
If a timeout occurs while waiting for a match, a TimeoutError is raised (and
any data received so far is lost).
However, if the remote end disconnects while waiting for a match, no error
is generated, and the data received so far is returned. It explicitly
rescues EOFError to do this.
This leads to difficult usage, because if you do
@telnet.waitfor(/prompt/)
and it returns, it could mean one of two things: either the string you were
waiting for was matched, or it wasn't matched and the far end disconnected.
The first is what you expect, and the second is likely to be an error
condition.
So I find that every waitfor call has to be wrapped, e.g.
res = @telnet.waitfor(/prompt/)
unless /prompt/ =~ res
raise EOFError # or handle this situation some other way
end
Now, perhaps the current behaviour is useful in some situations - you telnet
to a device, issue a command, and it returns some data and disconnects. But
I'd like to be able to say explicitly this is what should happen, e.g.
@telnet.waitfor(nil)
or
@telnet.waitfor(:eof)
However you'd have to have an option to Net::Telnet.new to enable this
behaviour, to maintain backwards compatibility.
Does anyone have any thoughts on this?
Thanks,
Brian.