Re: [Pharo-users] Naming parameters - conventions?

On Thursday 12 July 2018 03:54 AM, Tim Mackinnon wrote:

I was taught {“a”/“an”}DataType, so it would be:

#name: aString

It depends on the current level of abstraction. At the lowest levels, it is okay to use basic types like aString since classes (types) define behavior. If you are operating at a much higher level, say transfering money between two accounts, you would do: #transferMoney from: aPayer to: aPayee where both aPayer and aPayee could be anAccountHolder Essentially, the idea to keep the message part as close to normal statements as possible. The book "A Mentoring Course Smalltalk" by Andres Valloud covers this aspect in great detail. Regards .. Subbu