[Pharo-users] Use cases for methods with optional parameters

David Allouche david at allouche.net
Fri Jan 29 18:29:48 EST 2016


> On 28 Jan 2016, at 21:55, stepharo <stepharo at free.fr> wrote:
> Le 25/1/16 09:32, David Allouche a écrit :
>> - Morphic
>> - Morph
>> - addAlarm:*at:
>> - addAlarm:*after:
>> - startStepping*
>> - subMorphNamed:*
>> 
>> - Morphic
>> - MenuMorph
>> - add:*selector:*
>> - addToggle:*
>> - addUpdating:*
>> 
>> Some of those might not be simplified by default arguments, and some of those may require run-time default values. At least, they make interesting edge cases.
> Tx for the examples.
> 
> we should also use a fluid api and not these lengthly argument tedious list

That should probably be for another thread, but…

I am all for avoiding lengthy tedious argument lists that break my limited short term memory. What do you mean by "fluid api"?





More information about the Pharo-users mailing list