_

Dear all

I request permission to enable 'allow underscore selectors'
by default :)

Best
        -Tobias

I support the idea, because it makes it easier to load external code, but
we shouldn't use such names in the Trunk itself.

Levente

On Fri, 13 Mar 2015, Tobias Pape wrote:

> Dear all
>
> I request permission to enable 'allow underscore selectors'
> by default :)
>
> Best
> -Tobias
>
>

On 12-03-2015, at 5:29 PM, Levente Uzonyi <[hidden email]> wrote:

> I support the idea, because it makes it easier to load external code, but we shouldn't use such names in the Trunk itself.

Given that it seems to trigger complaints about the state of the method’s source every time you attempt to browse a method with _, I’d say not. Or, of course, fix the problem.

Though as everyone knows, using _ in variables is a Mortal Sin.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Press [ESC] to detonate or any other key to explode.

Why is this preference in the first place instead of simply always
allowing them?  If we wish to understand well enough to answer Tobias'
question, we probably should understand the trade-off to allowing
them.  So what is the trade-off?

Personally, I don't see myself ever using them and I agree with
Levente that we wouldn't in trunk but...  what is the harm to allow
someone to use underscores in selectors if they want to?


On Thu, Mar 12, 2015 at 7:29 PM, Levente Uzonyi <[hidden email]> wrote:

On 13.03.2015, at 01:33, tim Rowledge <[hidden email]> wrote:

> On 12-03-2015, at 5:29 PM, Levente Uzonyi <[hidden email]> wrote:
>
>> I support the idea, because it makes it easier to load external code, but we shouldn't use such names in the Trunk itself.
>
> Given that it seems to trigger complaints about the state of the method’s source every time you attempt to browse a method with _, I’d say not. Or, of course, fix the problem.
>

I hope my latest commit mitigates…

Best
        -Tobias

> Though as everyone knows, using _ in variables is a Mortal Sin.
>
> tim