asking browser for references to a class finds a method that merely refers to a symbol of the same name

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

asking browser for references to a class finds a method that merely refers to a symbol of the same name

timrowledge
Seriously? How did that happen?

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
"Bother," said Pooh. "Eeyore - ready two photon torpedoes and lock phasers on the Heffalump. Piglet, meet me in Transporter Room Three."


Reply | Threaded
Open this post in threaded view
|

Re: asking browser for references to a class finds a method that merely refers to a symbol of the same name

Eliot Miranda-2


On Fri, Jan 30, 2015 at 12:27 PM, tim Rowledge <[hidden email]> wrote:
Seriously? How did that happen?

I did it.  It's so that one finds usages such as

    Smalltalk classNamed: #Array

If it doesn't do that one's hosed  One can always use the allCallsOn: aClass binding if one wants the  more restrictive form.


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
"Bother," said Pooh. "Eeyore - ready two photon torpedoes and lock phasers on the Heffalump. Piglet, meet me in Transporter Room Three."

--
best,
Eliot


Reply | Threaded
Open this post in threaded view
|

Re: asking browser for references to a class finds a method that merely refers to a symbol of the same name

Chris Muller-3
In reply to this post by timrowledge
"Thorough Senders" preference?

On Fri, Jan 30, 2015 at 2:27 PM, tim Rowledge <[hidden email]> wrote:
> Seriously? How did that happen?
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> "Bother," said Pooh. "Eeyore - ready two photon torpedoes and lock phasers on the Heffalump. Piglet, meet me in Transporter Room Three."
>
>

Reply | Threaded
Open this post in threaded view
|

Re: asking browser for references to a class finds a method that merely refers to a symbol of the same name

Eliot Miranda-2


On Fri, Jan 30, 2015 at 12:41 PM, Chris Muller <[hidden email]> wrote:
"Thorough Senders" preference?

No.  The thorough senders preference controls whether scanning for literals descends into nested literal arrays.

On Fri, Jan 30, 2015 at 2:27 PM, tim Rowledge <[hidden email]> wrote:
> Seriously? How did that happen?
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> "Bother," said Pooh. "Eeyore - ready two photon torpedoes and lock phasers on the Heffalump. Piglet, meet me in Transporter Room Three."
--
best,
Eliot


Reply | Threaded
Open this post in threaded view
|

Re: asking browser for references to a class finds a method that merely refers to a symbol of the same name

timrowledge
In reply to this post by Eliot Miranda-2

On 30-01-2015, at 12:36 PM, Eliot Miranda <[hidden email]> wrote:

>
>
> On Fri, Jan 30, 2015 at 12:27 PM, tim Rowledge <[hidden email]> wrote:
> Seriously? How did that happen?
>
> I did it.  It's so that one finds usages such as
>
>     Smalltalk classNamed: #Array

Hmm, ok. It’s more than a bit disconcerting but I kinda see your logic. Can’t even really argue for double-checking against the ‘classNamed:’ since obviously anyone could come up with an analogous message that would screw that.


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Useful Latin Phrases:- Braccae illae virides cum subucula rosea et tunica Caledonia-quam elenganter concinnatur! = Those green pants go so well with that pink shirt and the plaid jacket!



Reply | Threaded
Open this post in threaded view
|

Re: asking browser for references to a class finds a method that merely refers to a symbol of the same name

Tobias Pape

On 30.01.2015, at 22:15, tim Rowledge <[hidden email]> wrote:

> On 30-01-2015, at 12:36 PM, Eliot Miranda <[hidden email]> wrote:
>
>>
>>
>> On Fri, Jan 30, 2015 at 12:27 PM, tim Rowledge <[hidden email]> wrote:
>> Seriously? How did that happen?
>>
>> I did it.  It's so that one finds usages such as
>>
>>    Smalltalk classNamed: #Array
>
> Hmm, ok. It’s more than a bit disconcerting but I kinda see your logic. Can’t even really argue for double-checking against the ‘classNamed:’ since obviously anyone could come up with an analogous message that would screw that.
>


Yes. For example, I have written code like this (don't ask why ;))

possibleRuleClasses

        ^ (self subclassesIfAvailable: #GRSlimeBlockLintRule),
           (self subclassesIfAvailable: #GRSlimeParseTreeLintRule)
                select: [:cls | cls name beginsWith: 'GR']

Best
        -Tobias