Ruby Issue Tracking System

12/04/2012

08:23 AM Ruby Feature #6762: Control interrupt timing

I was suggesting "interruptible" as a better alternative for
"async_interrupt_timing" or "control_interrupt". Can either be called
without a block? If so, does it change the way subsequent interrupts
are delivered?

I'd like... brent (Brent Roman)

06:53 AM Ruby Feature #6762: Control interrupt timing

Regarding ability of Thread.current.raise to be deferred,
if it works that way now, I'd vote to keep it this way.
Best not to have a special case for Thread.current.raise
If an application requires the special behavior, that's eas... brent (Brent Roman)

12/01/2012

04:23 AM Ruby Feature #6762: Control interrupt timing

OK. I see the logic in using the term "interrupt" if you are actually
trying to unify exceptions from other threads with handling of OS
signals. However, both of these are generally thought of as being
asynchronous events.

... brent (Brent Roman)

11/30/2012

07:23 PM Ruby Feature #6762: Control interrupt timing

Koichi,

Sorry about misspelling your name in my previous post. :-(

In reference to:
----------------
* thraed.c: add Thread.async_interrupted?.
This method check any defered async interrupts.

Ah, I want to say... brent (Brent Roman)

07:23 PM Ruby Feature #6762: Control interrupt timing

How about:

Thread.allow_exception(RuntimeError => :on_blocking){
while true
...

- brent

--
Posted via http://www.ruby-forum.com/. brent (Brent Roman)

06:29 PM Ruby Feature #6762: Control interrupt timing

I like this proposal.
It looks very similar to one I made five years ago on this thread:

www.ruby-forum.com/topic/135822

The key, of course, is to associate a (hidden) queue with each thread
for incoming exceptions from ot... brent (Brent Roman)

05/06/2009

11:31 AM Ruby Feature #1432: decrement and increment

=begin

Why is

a+=1

less elegant than

++a

However, I admit that using

(x=a; a+=1; x)

to replace

a++

is pretty evil looking. (The postfix variants *are* a pain to emulate
correctly)

Are there other ... brent (Brent Roman)

04/13/2009

01:12 PM Ruby Bug #1336: Change in string representation of Floats

=begin

I'm not sure I understand the difference between "mere string" and "human
readable" representations.
Could you give an example?

1.8 is similar enough to 1.9 that many straightforward scripts will run
without change.
Howe... brent (Brent Roman)

10:55 AM Ruby Bug #1336: Change in string representation of Floats

=begin

Perhaps I'm not understanding the question.
Consider:

s = "string"
s.inspect ==> "string" #this will round-trip
s.to_s ==> string #this lacks the required delimiters

s = :symbol
s.inspect ==> :symbo... brent (Brent Roman)

04/12/2009

03:59 AM Ruby Bug #1336: Change in string representation of Floats

=begin

Your latter example seems quite nice.
Especially if it would accept unabbreviated forms such as this:

0.9.to_s(precision: 4, width: 6) #=> " 9.000"

- brent



Nobuyoshi Nakada-2 wrote:
>
> Hi,
>
> At Sat, 11 Ap... brent (Brent Roman)