[#25936] [Bug:1.9] [rubygems] $LOAD_PATH includes bin directory — Nobuyoshi Nakada <nobu@...>

Hi,

10 messages 2009/10/05

[#25943] Disabling tainting — Tony Arcieri <tony@...>

Would it make sense to have a flag passed to the interpreter on startup that

16 messages 2009/10/05

[#26028] [Bug #2189] Math.atanh(1) & Math.atanh(-1) should not raise an error — Marc-Andre Lafortune <redmine@...>

Bug #2189: Math.atanh(1) & Math.atanh(-1) should not raise an error

14 messages 2009/10/10

[#26222] [Bug #2250] IO::for_fd() objects' finalization dangerously closes underlying fds — Mike Pomraning <redmine@...>

Bug #2250: IO::for_fd() objects' finalization dangerously closes underlying fds

11 messages 2009/10/22

[#26244] [Bug #2258] Kernel#require inside rb_require() inside rb_protect() inside SysV context fails — Suraj Kurapati <redmine@...>

Bug #2258: Kernel#require inside rb_require() inside rb_protect() inside SysV context fails

24 messages 2009/10/22

[#26361] [Feature #2294] [PATCH] ruby_bind_stack() to embed Ruby in coroutine — Suraj Kurapati <redmine@...>

Feature #2294: [PATCH] ruby_bind_stack() to embed Ruby in coroutine

42 messages 2009/10/27

[#26371] [Bug #2295] segmentation faults — tomer doron <redmine@...>

Bug #2295: segmentation faults

16 messages 2009/10/27

[ruby-core:25975] Re: turning off indentation warnings

From: Aaron Patterson <aaron@...>
Date: 2009-10-06 17:56:27 UTC
List: ruby-core #25975
On Sep 24, 2009, at 12:01 PM, Aaron Patterson wrote:

> On Sep 22, 2009, at 8:19 PM, Nobuyoshi Nakada wrote:
>
>> Hi,
>>
>> At Wed, 23 Sep 2009 11:49:45 +0900,
>> Ryan Davis wrote in [ruby-core:25725]:
>>> I've looked into adding a global variable. I think it looks better,
>>> but it requires modifying the parser to evaluate SOME expressions at
>>> parse time and I think that is a can of worms we don't want to open.
>>
>> I agree it's a worst idea.
>
> Yes, the global variable seems too hard.  Can we get this patch  
> applied (using magic comments)?  I will open a ticket if it helps.
>
>>>> +static void
>>>> +set_boolean(struct parser_params *parser, int *p, const char *val)
>>>
>>> Is this really necessary? I'd rather stick to ruby values and remove
>>> enable/yes/disable/no.
>>
>> What do you mean by `ruby values'?
>
> I think just "true" or "false" would be best, but I'm happy with  
> something that works.  ;-)

Bump...

---
Aaron Patterson
http://tenderlovemaking.com





In This Thread