Mmm. This may be a bug with “timeout” in that it doesn’t add its method
to Kernel. A thought.
-austin
···
–
austin ziegler * austin.ziegler@evault.com
-----Original Message-----
From: Sean O’Dell [mailto:sean@celsoft.com]
Sent: 28 May 2004 17.11
To: ruby-talk ML
Subject: Re: Calling global method
On Friday 28 May 2004 13:41, Austin Ziegler wrote:
On Friday 28 May 2004 13:02, Austin Ziegler wrote:
Well, I find it useful as I’m a bit stuck right now about how to
call a global method without producing some ugly code. It looks
like ugly is going to win, though, since there is no clean
built-in way to do it.
- What built-in method? Perhaps you’ve chosen the wrong method.
- If it’s not built in, why aren’t you boxing it yourself?
The timeout method, module “timeout.”
Sean O’Dell
At this point, I decided I would just grab the source and use a local copy of
it after I wrapped it all in Kernel. But looking at the source, I see two
copyright notices and nothing about licensing. Is this library released GPL
or something else I didn’t notice? Are all the libraries released with Ruby
these days covered by licenses kept elsewhere?
Sean O'Dell
···
On Friday 28 May 2004 14:54, Austin Ziegler wrote:
Mmm. This may be a bug with “timeout” in that it doesn’t add its method
to Kernel. A thought.
Actually, timeout is fine I think. I can call it using Timeout::timeout. I
thought I’d already tried that, but I probably thought I did and got
distracted. Anyway, timeout seems fine because it’s wrapped in its own
module. It DOES have one of those “private Object method” type of globals
though, and that’s what is documented. I guess it’s up to the developers to
put things in Kernel to make them properly global?
Sean O'Dell
···
On Friday 28 May 2004 14:54, Austin Ziegler wrote:
Mmm. This may be a bug with “timeout” in that it doesn’t add its method
to Kernel. A thought.