Ruby 1.9.3 released • Hacker News Board

Re: Ruby 1.9.3 released

#41

Post by aeontech » Mon, Oct 31, 2011, 7:46 AM UTC

tibastral2 wrote: post #20

to install with rvm : first update rvm, bash https://rvm.beginrescueend.com/install/rvm ) then rvm install 1.9.3 and rvm use 1.9.3 --default And you are on fire

thanks

Re: Ruby 1.9.3 released

#42

Post by mrinterweb » Mon, Oct 31, 2011, 8:05 AM UTC

catch23 wrote: post #36

mrinterweb wrote: post #34

Earlier quoted context omitted.

The lack of a working ruby-debug19 has been the only thing keeping me from using 1.9.3.

Just use pry, it's not really a debugger replacement, but it's useful in most cases that ruby-debug19 would be used. http://rubygems.org/gems/pry

I've used pry. I like pry, but it really does not fill the need of a debugger.

Re: Ruby 1.9.3 released

#43

Post by vidarh » Mon, Oct 31, 2011, 11:08 AM UTC

Game_Ender wrote: post #21

lilpirate wrote: post #7

Earlier quoted context omitted.

Yeah! I plan on to start learning Ruby.

Give Python a look as well. Also, never try to embed Ruby in a C/C++ application it's not designed for it.

It's trivial to embed Ruby in C/C++.

Re: Ruby 1.9.3 released

#44

Post by taf2 » Sat, Nov 05, 2011, 3:25 AM UTC

wycats wrote: post #28

riffraff wrote: post #26

Earlier quoted context omitted.

1.8 had green threads and when the interpreter blocked on some operations it would block all the threads. 1.9 uses native threads but it has a global interpreter lock which has known issues. I am not sure what the improvements to locking in 1.9.3, as the changelog has quite a few commits related to that.

In both Ruby 1.8 and 1.9, Ruby code will not cause all threads to block when the CPU is idle. However, poorly coded C libraries that blocked on IO without providing Ruby a file descriptor (via rb_thread_select) could cause all threads to block. Those libraries have largely been fixed or replaced (e.g. mysql with mysql2). Ruby 1.9.2 also provides a mechanism for C code to release the GIL if it does not involve any Rub…

rb_thread_select is marked deprecated in 1.9.3... so what's the alternative?

Re: Ruby 1.9.3 released

#45

Post by taf2 » Sat, Nov 05, 2011, 3:56 AM UTC

taf2 wrote: post #44

wycats wrote: post #28

Earlier quoted context omitted.

In both Ruby 1.8 and 1.9, Ruby code will not cause all threads to block when the CPU is idle. However, poorly coded C libraries that blocked on IO without providing Ruby a file descriptor (via rb_thread_select) could cause all threads to block. Those libraries have largely been fixed or replaced (e.g. mysql with mysql2). Ruby 1.9.2 also provides a mechanism for C code to release the GIL if it does not involve any Rub…

rb_thread_select is marked deprecated in 1.9.3... so what's the alternative?

ok... replying to myself here... I think if you're using rb_thread_select the answer may be... use select(2) in an rb_thread_blocking_region callback... still not convinced this is better...