[Pharo-dev] Question on KmGlobalDispatcher

ducasse stepharo at netcourrier.com
Wed Feb 20 13:42:20 EST 2019

Thanks Ben. 
This is cool. I proposed to David to do a pair screen session but my agenda
will return soon to chaos :).


> On 20 Feb 2019, at 16:58, Ben Coman <btc at openinworld.com> wrote:
> Hi David,
> I invite you to consider this an opportunity to submit a PR to fix it.
> I'm happy to walk you though the process if you ping me on Discord chat.
> I remember it felt cool to have my first code integrated.
> Pharo is yours.
> cheers -ben
> On Wed, 20 Feb 2019 at 02:16, ducasse <stepharo at netcourrier.com <mailto:stepharo at netcourrier.com>> wrote:
> Hello David 
> Indeed this is a good catch. 
> Can you open a bug entry on github? 
> Else I will do it but this is cool to get involved that way
>> On 19 Feb 2019, at 17:37, David Richards <david.i.richards.iii at gmail.com <mailto:david.i.richards.iii at gmail.com>> wrote:
>> Why does the class name KmGlobalDispatcher have a small 'm'? 
>> Should it be more consistently named KMGlobalDispatcher, as all other classes in package: 'Keymapping-Core'?
>> Object subclass: #KmGlobalDispatcher
>> 	instanceVariableNames: 'dispatcher'
>> 	classVariableNames: ''
>> 	package: 'Keymapping-Core'
>> Just curious why this name seems inconsistent. I don't recall seeing an inconsistency with class name prefixes in any other package group. Is this just a mistake, or rather an opportunity to learn something interesting about how classes should be named in Pharo? As a beginner, I'm not sure which.
>> Thanks
>> David

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20190220/6c78a455/attachment.html>

More information about the Pharo-dev mailing list