[#5218] Ruby Book Eng tl, ch1 question — Jon Babcock <jon@...>

13 messages 2000/10/02

[#5404] Object.foo, setters and so on — "Hal E. Fulton" <hal9000@...>

OK, here is what I think I know.

14 messages 2000/10/11

[#5425] Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...>

18 messages 2000/10/11
[#5427] RE: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — OZAWA -Crouton- Sakuro <crouton@...> 2000/10/11

At Thu, 12 Oct 2000 03:49:46 +0900,

[#5429] Re: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...> 2000/10/11

Thanks for the input.

[#5432] Re: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Yasushi Shoji <yashi@...> 2000/10/11

At Thu, 12 Oct 2000 04:53:41 +0900,

[#5516] Re: Some newbye question — ts <decoux@...>

>>>>> "D" == Davide Marchignoli <marchign@di.unipi.it> writes:

80 messages 2000/10/13
[#5531] Re: Some newbye question — matz@... (Yukihiro Matsumoto) 2000/10/14

Hi,

[#5544] Re: Some newbye question — Davide Marchignoli <marchign@...> 2000/10/15

On Sat, 14 Oct 2000, Yukihiro Matsumoto wrote:

[#5576] Re: local variables (nested, in-block, parameters, etc.) — Dave Thomas <Dave@...> 2000/10/16

matz@zetabits.com (Yukihiro Matsumoto) writes:

[#5617] Re: local variables (nested, in-block, parameters, etc.) — "Brian F. Feldman" <green@...> 2000/10/16

Dave Thomas <Dave@thomases.com> wrote:

[#5705] Dynamic languages, SWOT ? — Hugh Sasse Staff Elec Eng <hgs@...>

There has been discussion on this list/group from time to time about

16 messages 2000/10/20
[#5712] Re: Dynamic languages, SWOT ? — Charles Hixson <charleshixsn@...> 2000/10/20

Hugh Sasse Staff Elec Eng wrote:

[#5882] [RFC] Towards a new synchronisation primitive — hipster <hipster@...4all.nl>

Hello fellow rubyists,

21 messages 2000/10/26

[ruby-talk:5902] Re: [RFC] Towards a new synchronisation primitive

From: Hugh Sasse Staff Elec Eng <hgs@...>
Date: 2000-10-27 09:12:57 UTC
List: ruby-talk #5902
On Fri, 27 Oct 2000, hipster wrote:

> The proposed syntax requires a new keyword `synchronized', and a new method
> `synchronize' on class Object. For brevity, the keyword `sync' and method
> Object.sync could be considered.

Please don't call it 'sync'.  There is a Unix command of this name
already, which may cause confusion.  I think 'synch" would be OK though.


Random (half-baked) thoughts:

I'm not sure about the need for

    def synch method
        ...
    end

if an instance can have @variables that are synchronisable. Would 
that not remove the need to say the method itself is synchronisable?
It only needs to synch if it touches something "critical".

If 
    class synch Thing
        def a
            b
            ...
        emd

        def b
            ...
        end
    end

then when a invokes b, it is the same instance that holds the lock, so
deadlock could be avoided.  The only time you cannot get into your house
is if somebody ELSE has the only key; if you have it that is OK.  Or is
that too simplistic?  This area is full of subtleties....

	Hugh


In This Thread