> On 30 Aug 2018, at 06:36, Tim Mackinnon <[email protected]> wrote:
>
> I am looking at porting my missing class creation code into Pharo 7, and I
> notice there is a DynamicMessageImplementor that does this for methods - but
> I’m wondering why when we create a missing method with ‘self
> souldBeImplemented.’ with a trailing “.”?
>
> The Smalltalk style guide normally says the last statement shouldn’t have a
> dot - and I notice some recent cleanups removed some dots on methods
> (presumably the formatter).
>
> This is a bit of a special case as the intent is to replace that method - but
> shouldn’t we create without the dot to set a good example anyway?
>
> If so, I can include that change in my pr.
>
I think there are both schools around… with some preference of no . at the end.
Sometimes I think that a system that would have a good pretty printer and
*always* pretty print would be nice: you would configure this once, and all code
would be shown in your “best readable” style…
Marcus
