Re: [Pharo-users] Message naming

2013-11-13 Thread Stéphane Ducasse
> Kilon, great reflection. > We should have Pharo display Pharo Zen as exposed in Pharo Vision: :) > Pharo Zen > > Our values and convictions are condensed in this simple list. > > Easy to understand, easy to learn from, easy to change. Objects all the way > down. > Examples to learn from.

Re: [Pharo-users] Message naming

2013-11-13 Thread kilon alios
What I tried to say here was that it was a mistake to blame the language itself for code design. Sure a language may have some ugly sides to it, it may even make it not so easy to create clean code but in the end of the day clean and readable code is up to the coder at least 90% . I would not say

Re: [Pharo-users] Message naming

2013-11-13 Thread Ignacio Matías Sniechowski
Kilon, great reflection. We should have Pharo display Pharo Zen as exposed in Pharo Vision: Pharo Zen Our values and convictions are condensed in this simple list. Easy to understand, easy to learn from, easy to change. Objects all the way down. Examples to learn from. Fully dynamic and malleabl

Re: [Pharo-users] Message naming

2013-11-13 Thread Bahman Movaqar
Kilon, I believe there's a subtle difference between Python, Java, Ruby and Scala on one side and Smalltalk on the other: All those 4 languages are more or less implemented as OO languages with the famous statement "everything is an object". However they are syntactically and semantically designed

Re: [Pharo-users] Message naming

2013-11-13 Thread kilon alios
I dont know exactly what you mean by eforced OOP by design. Pharo design principles are not written in stone, just good habits people picked along the way and they are to be found in python as well. Python actually takes OO very deply , sure if , else, while are language constructs but rest assured

Re: [Pharo-users] Message naming

2013-11-13 Thread Bahman Movaqar
@Sven > There is not necessarily a right and a wrong way. Design is hard to > explain, I am not going to try. Sorry ;-) Of course! I was just trying to find out the design *norm* for a small problem; to become familiar with the popular way of thought among Smalltalk'ers. @kilon Thanks. I think

Re: [Pharo-users] Message naming

2013-11-13 Thread Sven Van Caekenberghe
Hi Bahman, On 13 Nov 2013, at 09:19, Bahman Movaqar wrote: > On 11/13/2013 11:39, Bahman Movaqar wrote: >> On 11/13/2013 11:13, Bahman Movaqar wrote: >>> Let's say I have a method with signature in a language like Java as below: >>> gregorianDayToJulianDay(year, month, day) >>> >>> What could

Re: [Pharo-users] Message naming

2013-11-13 Thread kilon alios
Thats not only the Pharo, the Squeak, way, the Python way, the Ruby way . its the logical way GregorianDate >> toJulian You have a class then you have a method . You want to extend your method ? why increase the size of method ? You just create a new class for it. I have 3 rules when I cod

Re: [Pharo-users] Message naming

2013-11-13 Thread Stéphane Ducasse
did you check acancagua (unit and time) or chronos (more complete calendar) package Stef On Nov 13, 2013, at 9:19 AM, Bahman Movaqar wrote: > On 11/13/2013 11:39, Bahman Movaqar wrote: >> On 11/13/2013 11:13, Bahman Movaqar wrote: >>> Let's say I have a method with signature in a language l

Re: [Pharo-users] Message naming

2013-11-13 Thread Bahman Movaqar
On 11/13/2013 11:39, Bahman Movaqar wrote: > On 11/13/2013 11:13, Bahman Movaqar wrote: >> Let's say I have a method with signature in a language like Java as below: >> gregorianDayToJulianDay(year, month, day) >> >> What could be a proper naming for this method in Smalltalk? I'm a bit >> confus

Re: [Pharo-users] Message naming

2013-11-13 Thread Bahman Movaqar
On 11/13/2013 11:22, jtuc...@objektfabrik.de wrote: > Bahman, > > Am 13.11.13 08:43, schrieb Bahman Movaqar: >> Let's say I have a method with signature in a language like Java as >> below: >>gregorianDayToJulianDay(year, month, day) >> >> What could be a proper naming for this method in Smallt

Re: [Pharo-users] Message naming

2013-11-13 Thread Sven Van Caekenberghe
On 13 Nov 2013, at 08:52, jtuc...@objektfabrik.de wrote: > Bahman, > > Am 13.11.13 08:43, schrieb Bahman Movaqar: >> Let's say I have a method with signature in a language like Java as below: >> gregorianDayToJulianDay(year, month, day) >> >> What could be a proper naming for this method in S

Re: [Pharo-users] Message naming

2013-11-13 Thread Bahman Movaqar
On 11/13/2013 11:13, Bahman Movaqar wrote: > Let's say I have a method with signature in a language like Java as below: > gregorianDayToJulianDay(year, month, day) > > What could be a proper naming for this method in Smalltalk? I'm a bit > confused as I'm so used to the concept of methods being

Re: [Pharo-users] Message naming

2013-11-12 Thread jtuc...@objektfabrik.de
Bahman, Am 13.11.13 08:43, schrieb Bahman Movaqar: Let's say I have a method with signature in a language like Java as below: gregorianDayToJulianDay(year, month, day) What could be a proper naming for this method in Smalltalk? I'm a bit confused as I'm so used to the concept of methods bei

[Pharo-users] Message naming

2013-11-12 Thread Bahman Movaqar
Let's say I have a method with signature in a language like Java as below: gregorianDayToJulianDay(year, month, day) What could be a proper naming for this method in Smalltalk? I'm a bit confused as I'm so used to the concept of methods being "verbs" which accept some arguments. I'd appreciate