[#15359] Timeout::Error — Jeremy Thurgood <jerith@...>

Good day,

41 messages 2008/02/05
[#15366] Re: Timeout::Error — Eric Hodel <drbrain@...7.net> 2008/02/06

On Feb 5, 2008, at 06:20 AM, Jeremy Thurgood wrote:

[#15370] Re: Timeout::Error — Jeremy Thurgood <jerith@...> 2008/02/06

Eric Hodel wrote:

[#15373] Re: Timeout::Error — Nobuyoshi Nakada <nobu@...> 2008/02/06

Hi,

[#15374] Re: Timeout::Error — Jeremy Thurgood <jerith@...> 2008/02/06

Nobuyoshi Nakada wrote:

[#15412] Re: Timeout::Error — Nobuyoshi Nakada <nobu@...> 2008/02/07

Hi,

[#15413] Re: Timeout::Error — Jeremy Thurgood <jerith@...> 2008/02/07

Nobuyoshi Nakada wrote:

[#15414] Re: Timeout::Error — Nobuyoshi Nakada <nobu@...> 2008/02/07

Hi,

[#15360] reopen: can't change access mode from "w+" to "w"? — Sam Ruby <rubys@...>

I ran 'rake test' on test/spec [1], using

16 messages 2008/02/05
[#15369] Re: reopen: can't change access mode from "w+" to "w"? — Nobuyoshi Nakada <nobu@...> 2008/02/06

Hi,

[#15389] STDIN encoding differs from default source file encoding — Dave Thomas <dave@...>

This seems strange:

21 messages 2008/02/06
[#15392] Re: STDIN encoding differs from default source file encoding — Yukihiro Matsumoto <matz@...> 2008/02/06

Hi,

[#15481] very bad character performance on ruby1.9 — "Eric Mahurin" <eric.mahurin@...>

I'd like to bring up the issue of how characters are represented in

16 messages 2008/02/10

[#15528] Test::Unit maintainer — Kouhei Sutou <kou@...>

Hi Nathaniel, Ryan,

22 messages 2008/02/13

[#15551] Proc#curry — ts <decoux@...>

21 messages 2008/02/14
[#15557] Re: [1.9] Proc#curry — David Flanagan <david@...> 2008/02/15

ts wrote:

[#15558] Re: [1.9] Proc#curry — Yukihiro Matsumoto <matz@...> 2008/02/15

Hi,

[#15560] Re: Proc#curry — Trans <transfire@...> 2008/02/15

[#15585] Ruby M17N meeting summary — Martin Duerst <duerst@...>

This is a rough translation of the Japanese meeting summary

19 messages 2008/02/18

[#15596] possible bug in regexp lexing — Ryan Davis <ryand-ruby@...>

current:

17 messages 2008/02/19

[#15678] Re: [ANN] MacRuby — "Rick DeNatale" <rick.denatale@...>

On 2/27/08, Laurent Sansonetti <laurent.sansonetti@gmail.com> wrote:

18 messages 2008/02/28
[#15679] Re: [ANN] MacRuby — "Laurent Sansonetti" <laurent.sansonetti@...> 2008/02/28

On Thu, Feb 28, 2008 at 6:33 AM, Rick DeNatale <rick.denatale@gmail.com> wrote:

[#15680] Re: [ANN] MacRuby — Yukihiro Matsumoto <matz@...> 2008/02/28

Hi,

[#15683] Re: [ANN] MacRuby — "Laurent Sansonetti" <laurent.sansonetti@...> 2008/02/28

On Thu, Feb 28, 2008 at 1:51 PM, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:

From: "David A. Black" <dblack@...>
Date: 2008-02-19 20:01:13 UTC
List: ruby-core #15610
Hi --

I'm trying to get a fix on thread behavior in 1.9 vs. 1.8.6, and the
following things seem odd to me (unless I've just slept through some
known changes, which is always possible).

Doing this:

$ ruby19 -ve 'Thread.new { puts "a" }'
ruby 1.9.0 (2008-02-15 revision 0) [i686-darwin9.1.0]

always results in no output (except the version).

The same thing in 1.8.6 always puts's "a":

$ ruby -ve 'Thread.new { puts "a" }'
ruby 1.8.6 (2007-03-13 patchlevel 0) [i686-darwin8.10.1]
a

So I figure that somehow the killing of the new thread upon exit is
"winning" over the execution of the thread. I guess that's OK (?).
Anyway, this tends to support that interpretation:

$ ruby19 -e 'Thread.new { puts "a" }; sleep 0.01'
a

I then did a few more little tests. I'm leaving in all the -v stuff,
since that's how it was, but the main point is that 1.8.6 seems to
always do this:

$ ruby -ve 'Thread.new { puts "a" }; puts "b"'
ruby 1.8.6 (2007-03-13 patchlevel 0) [i686-darwin8.10.1]
a
b

while 1.9 does a variety of things, presumably depending on
scheduling:

$ ruby19 -ve 'Thread.new { puts "a" }; puts "b"'
ruby 1.9.0 (2008-02-15 revision 0) [i686-darwin9.1.0]
ba

$ ruby19 -ve 'Thread.new { puts "a" }; puts "b"'
ruby 1.9.0 (2008-02-15 revision 0) [i686-darwin9.1.0]
b
$ ruby19 -ve 'Thread.new { puts "a" }; puts "b"'
ruby 1.9.0 (2008-02-15 revision 0) [i686-darwin9.1.0]
ba

$ ruby19 -ve 'Thread.new { puts "a" }; puts "b"'
ruby 1.9.0 (2008-02-15 revision 0) [i686-darwin9.1.0]
ba
$

(That last one had both letters but only one newline.)

I'm not quite sure what all of this adds up to, in terms of predicting
thread behavior at or near the end of a program. That one can't? :-)


David

-- 
Upcoming Rails training from David A. Black and Ruby Power and Light:
   ADVANCING WITH RAILS, April 14-17 2008, New York City
   CORE RAILS, June 24-27 2008, London (Skills Matter)
See http://www.rubypal.com for details, and stay
tuned for dates in Berlin!

In This Thread

Prev Next