[#1579] arity bug? — "Christoph" <chr_news@...>
Hi,
5 messages
2003/10/05
[#1588] FreeBSD problem with processes — Laurent Sansonetti <pinux@...>
Hi all,
1 message
2003/10/07
[#1591] Re: Yielding to a block from a proc? — george.marrows@...
> > Is this right? Is this pathological? Is it a bug? Is there
6 messages
2003/10/08
[#1596] PATCH: Revive NextStep, OpenStep, Rhapsody ports — Eric Sunshine <sunshine@...>
Hello,
7 messages
2003/10/09
[#1597] Re: PATCH: Revive NextStep, OpenStep, Rhapsody ports
— matz@... (Yukihiro Matsumoto)
2003/10/09
Hi,
[#1600] CVS access — Sean Russell <ser@...>
Hiya,
8 messages
2003/10/09
[#1611] set_trace_func/Array#fetch error — "Nathaniel Talbott" <nathaniel@...>
I've reduced the error I reported in ruby-talk:84013 to the following code:
17 messages
2003/10/11
[#1612] Re: set_trace_func/Array#fetch error
— ts <decoux@...>
2003/10/11
>>>>> "N" == Nathaniel Talbott <nathaniel@talbott.ws> writes:
[#1616] Re: set_trace_func/Array#fetch error
— "Nathaniel Talbott" <nathaniel@...>
2003/10/11
ts [mailto:decoux@moulon.inra.fr] wrote:
[#1617] Re: set_trace_func/Array#fetch error
— ts <decoux@...>
2003/10/11
>>>>> "N" == Nathaniel Talbott <nathaniel@talbott.ws> writes:
[#1618] Re: set_trace_func/Array#fetch error
— "Nathaniel Talbott" <nathaniel@...>
2003/10/11
ts [mailto:decoux@moulon.inra.fr] wrote:
[#1634] stringy range bug — "Christoph" <chr_news@...>
Hi,
6 messages
2003/10/15
[#1640] SystemStackError in embedding — Sentinel <sentinel27@...>
Hi, I am just now trying to embed ruby into my apprication
8 messages
2003/10/18
Success story. Ruby 1.8.0 + OpenSSL for Ruby 2
From:
Vladimir Shahov <v.shahov@...>
Date:
2003-10-07 17:35:40 UTC
List:
ruby-core #1589
Hi Last time (from begining of 2003 to now) we are intensively using different versions of ruby (1.7.2, 1.7.3, 1.8.0pre1, *pre2, -final) and ruby-openssl (0.1.3 and 0.2.0pre). Ruby+ossl used by complex application, including own httpsd server and completely written on ruby language. Target platform: Alt Linux Master 2.2, Debian GNU/Linux (stable and testing). Old ruby-openssl (0.1.3) was quite unstable (segmentation fault with intensive multithreading). Several workarounds was maked: SIG_SEGV handle and non-blocking syswrite. Migration on ruby 1.8.0-final and it's "OpenSSL for Ruby 2" make things good. No one "segmentation faults" for last week. Great job, guys! PS: Special thanks to Alexander Bokovoy for the openssl 0.9.6 backport request. -- Vladimir Shahov, icq 78193930