On 2013-05-28 12:07, Damien Cassou wrote:
> On Tue, May 28, 2013 at 7:13 AM, Bahman Movaqar <
[hidden email]> wrote:
>> I noticed that since there is no `import' statement in Pharo, class
>> names can easily conflict. What is the common naming strategy that you
>> people use to avoid that?
>
>
> the first two letters are often an indication of the package. E.g.,
> PRPage for a Page class in the Pier package, ZnEasy for the Easy class
> in the Zinc package...
Thanks. I'll follow that convention.
BTW I assume there is no central place to check if the two letter
combination has already been taken or not, right?
--
Bahman Movaqar (
http://BahmanM.com)
ERP Evaluation, Implementation, Deployment Consultant