extension not appearing under package(-tag?)

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

extension not appearing under package(-tag?)

Ben Coman
I'm not sure what to make of this... I notice that the class side of
Object has protocol *Tools-Debugger contains method
#canonicalArgumentName, but class side of that package/tag does not
show #canonicalArgumentName, which instead appears under parent
"Tools".

Also btw, I notice package Tools-Debugger contain KeyPrinterMorph and
SyntaxErrorDebugger classes which seem to have no class references.
Not that every class needs to be referenced, but just floating this
observation in case someone knew if they need to be cleaned up or
moved.

cheers -ben

Reply | Threaded
Open this post in threaded view
|

Re: extension not appearing under package(-tag?)

Nicolai Hess


2015-08-10 15:12 GMT+02:00 Ben Coman <[hidden email]>:
I'm not sure what to make of this... I notice that the class side of
Object has protocol *Tools-Debugger contains method
#canonicalArgumentName, but class side of that package/tag does not
show #canonicalArgumentName, which instead appears under parent
"Tools".

This looks like a bug.
 

Also btw, I notice package Tools-Debugger contain KeyPrinterMorph and
SyntaxErrorDebugger classes which seem to have no class references.

At least SyntaxErrorDebugger is used.
SyntaxErrorNotification opens a SyntaxErrorDebugger.


 
Not that every class needs to be referenced, but just floating this
observation in case someone knew if they need to be cleaned up or
moved.

cheers -ben


Reply | Threaded
Open this post in threaded view
|

Re: extension not appearing under package(-tag?)

Ben Coman
On Mon, Aug 10, 2015 at 9:50 PM, Nicolai Hess <[hidden email]> wrote:
>
>
> 2015-08-10 15:12 GMT+02:00 Ben Coman <[hidden email]>:
>> Also btw, I notice package Tools-Debugger contain KeyPrinterMorph and
>> SyntaxErrorDebugger classes which seem to have no class references.
>
> At least SyntaxErrorDebugger is used.
> SyntaxErrorNotification opens a SyntaxErrorDebugger.

Ahh, now I see...
    SyntaxErrorNotification>>registerToolsOn: registry
           "Add ourselves to registry. See [Smalltalk tools]"
           registry register: self as: #syntaxErrorDebugger.

Now I wonder if there is any absolute requirement that the first
letter of that symbol needs to be lowercase.  After all its not a
message.
If it was "registry register: self as: #SyntaxErrorDebugger" then
"Analyse > Class refs" would find it.  Obviously not applicable to all
cases
of registering tools, but could that be reasonable in this case?

cheers -ben