[Pharo-project] [squeak-dev] some thoughts on coding practices.

Stéphane Ducasse stephane.ducasse at inria.fr
Sun Sep 6 15:07:28 EDT 2009


>     (2) I wanted to make a subclass, but then discovered
>>>> RFBServer which
>>>> I need actually hard codes a reference to InputEventSensor versus
>>>> saying
>>>>       InputEventHandler defaultClass  (or something)
>>
>> 	-> yes not hardcoding class is a good design and it should be
>> reinforced.
>
> So is there a Lint rule for this or someone thinking of doing that
> cleanup? Or a
> bug? report?

I have to check for the smallLint rule.
For now open a ticket
>
>>> I fixed this in Refactoring-Spelling-lr.7, so that the spell checker
>>> is only initialized when it is actually used.
>>>
>>> It looks to me that you are using a Pharo-Dev image, but I guess you
>>> would rather use a Pharo-Core image? Maybe the Pharo-Core image
>>> should
>>> be placed more prominent on the download page, I've seen numerous
>>> experienced people at ESUG downloading the "wrong" image.
>>
>> Yes which tells me that we should also iron pharo-dev.
>
>
> Er well I thought the iPhone users would *like* to access the dev
> image? Is that wrong?

No but we got some glitches with the different browsers related to OB
because code diverged and we would love to get it on track but david  
is working on
papers :)

Stef
>
>
> --
> =
> =
> =
> = 
> = 
> ======================================================================
> John M. McIntosh <johnmci at smalltalkconsulting.com>   Twitter:
> squeaker68882
> Corporate Smalltalk Consulting Ltd.  http:// 
> www.smalltalkconsulting.com
> =
> =
> =
> = 
> = 
> ======================================================================
>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project





More information about the Pharo-dev mailing list