Issue 4294 in pharo: With only one Paragraph class, there is no need for #paragraphClass

Status: FixToInclude
Owner: [hidden email]
Labels: Milestone-1.3

New issue 4294 by [hidden email]: With only one Paragraph class,  
there is no need for #paragraphClass
http://code.google.com/p/pharo/issues/detail?id=4294

With only one Paragraph class, there is no need for #paragraphClass

fix attached

Attachments:
        ParaGraphSimpler.1.cs  2.2 KB


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Closed

Comment #1 on issue 4294 by [hidden email]: With only one Paragraph  
class, there is no need for #paragraphClass
http://code.google.com/p/pharo/issues/detail?id=4294

in 13219


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #2 on issue 4294 by [hidden email]: With only one Paragraph  
class, there is no need for #paragraphClass
http://code.google.com/p/pharo/issues/detail?id=4294

a messages like xyzClass , usually used to retrieve the class and then send  
#new to it. It is much better to use #newXyz for this purpose, so an object  
which responsible for providing an instance of given class, could decide  
what to do and how initialize it, before passing to requester.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker