[#6363] Re: rescue clause affecting IO loop behavior — ts <decoux@...>

>>>>> "D" == David Alan Black <dblack@candle.superlink.net> writes:

17 messages 2000/11/14
[#6367] Re: rescue clause affecting IO loop behavior — David Alan Black <dblack@...> 2000/11/14

Hello again --

[#6582] best way to interleaf arrays? — David Alan Black <dblack@...>

Hello --

15 messages 2000/11/26

[#6646] RE: Array Intersect (&) question — Aleksi Niemel<aleksi.niemela@...>

Ross asked something about widely known and largely ignored language (on

23 messages 2000/11/29
[#6652] RE: Array Intersect (&) question — rpmohn@... (Ross Mohn) 2000/11/29

aleksi.niemela@cinnober.com (Aleksi Niemel) wrote in

[#6723] Re: Array Intersect (&) question — Mathieu Bouchard <matju@...> 2000/12/01

> >Use a hash. Here's code to do both and more. It assumes that

[#6656] printing/accessing arrays and hashes — raja@... (Raja S.)

I'm coming to Ruby with a Python & Common Lisp background.

24 messages 2000/11/30

[ruby-talk:6633] RE: Why is WeakRef#__getobj__ missing from the p ickaxe book?

From: Aleksi Niemel<aleksi.niemela@...>
Date: 2000-11-29 15:07:34 UTC
List: ruby-talk #6633
Cullen J O'Neill proposed:

> My question is, isn't it a better idea to just get a real reference
> to the object using __getobj__?
> 
> ----
> if ref.weakref_alive?
>   real_ref = ref.__getobj__

I don't know much about weak references, but I'd guess you risk losing the
real object with above code. I feel I would not rely on the fact there
happens no GC between alive? and __getobj__.

Nevertheless I guess some combination of your's and book's versions would be
ideal, while pretty wordy. I don't like the idea GC is disabled, at least
for longer periods.

Maybe there's demand for 

  weakref.if_alive do |ref|
    # stuff
  end

And hide the ugly semantics of GC disabling, and allow immediate GC
enabling.

	- Aleksi

In This Thread

Prev Next