I should have remembered that, seeing that I've done 41/42 of the Pharo exercisms, and am currently doing the F# ones in my spare time, which I have had very little of lately. I have started using the <BADNAME[: 'reason']> annotation in such cases to remind me not to fix the code. Looking back at my solution, I see that my irritation at yet another "Pharo" exercism that had no significant connection with *OOP* as such masked the irritation I should have felt at the bad name. I also recall now my annoyance at exercism.io's frequent practice of omitting key parts of specifications but including tests for them.
Seriously, sometimes it's worth it to write good code and then write glue code to the required interface. On Tue, 7 Jan 2020 at 18:50, xap <x...@router.33mail.com> wrote: > > richard, fwiw Roeloff mentioned earlier that the message-name was provided by > the exercise set he's following, and isn't of his invention: > http://forum.world.st/is-this-better-regarding-naming-thigs-tp5109389p5109471.html > . he sh/could fwd your note/s to the course-author ;) > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >
