[#796] Re: value of assignment (Re: Order of the value of an expression changed? (PR#579)) — Sean Chittenden <sean@...>
> [email protected] wrote:
Hi,
> |I have read the thread and I think this is a pretty bad change. I
Hi,
> > #BEGIN test.rb
Hi,
Hi --
Hi,
Hi --
Hi,
Hi,
Hi,
what about if attr_accessor :foo defined three methods - #foo, #foo=, and
> |What was wrong with having the receiver set the return value though?
Sean Chittenden <[email protected]> writes:
> > f = Foo.new()
>>>>> "J" == J Herre <[email protected]> writes:
On 11 Feb 2003 at 11:13, Sean Chittenden wrote:
[#801] class of $1, $2 in 1.8.0 — dblack@...
Hi --
Hi,
Hi --
Hi,
Hi --
J.Herre <[email protected]> writes:
Hi --
On Sat, 8 Feb 2003 06:52:17 +0900
Hi --
On Friday, February 7, 2003, at 03:15 PM, [email protected]
[#851] Alternate GC ? — Mathieu Bouchard <matju@...>
[#875] OpenSSL for Ruby 0.2.0-pre0 — Michal Rokos <michal@...>
Hi everybody!
[#889] Bob Jenkins' hashing implementation in Ruby — Mauricio Fern疣dez <batsman.geo@...>
>>>>> "M" == Mauricio Fern疣dez <Mauricio> writes:
On Sat, Mar 01, 2003 at 08:42:40PM +0900, ts wrote:
>>>>> "M" == Mauricio Fern疣dez <Mauricio> writes:
On Sat, Mar 01, 2003 at 10:03:47PM +0900, ts wrote:
>>>>> "M" == Mauricio Fern疣dez <Mauricio> writes:
On Sat, Mar 01, 2003 at 10:10:35PM +0900, ts wrote:
Hi,
[#890] String and (repost) MemLeak — Michal Rokos <michal@...>
Hi,
Hi,
Hi,
Hi,
Hi,
Re: Alternate GC ?
On 12.02 04:01, Mathieu Bouchard wrote: > I think I recall that Ruby 1.8 was supposed to get a new garbage > collector. It appears not to be the case. However, I wonder whether > there's a patch that I could apply to Ruby (1.6.8 or 1.8.0) that would > improve the "realtimeness" of Ruby in any way. Specifically, I mean > anything that would make the worst-case duration of a GC interruption > smaller. There exists a patch which implements a non-copying generational GC for ruby. But the patch[1] is quite old (1.4.4). The code looks quite easy to understand and porting it to 1.8 should be possible. "Ruby Hacking Guide" (a japanese book) has apparently some information on the topic too. Ruby's own GC is very clean code so it should provide you with enough information about the interfaces. However you need to be aware that realtime and generational GC are for different purposes. A generational GC reduces the average time it takes to sweep, while a real time collector makes guarantees about the worst-case. I haven't heard of any real-time collector for Ruby. I don't know what happened to the 1.8 generational GC plan, maybe someone more knowledgeable would like to enlighten us. 1) http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-dev/9990 - Einar Karttunen