When the "sending site" is an actual end-user, API unification eases
their use of the system.  For example, we have a single user-input
that is interpreted on the fly and constructed into a full query
decision tree, this simplifies and unifies the syntax.

Similarly, when dragging an object argument to a Maui Parameter-Holder
doesn't require the user to make a collection.

Any time 1..n objects may be an argument, #asArray _unifies_ the API
to accept, equally, a collection or single-object.

Regards,
  Chris



On Sat, Jun 19, 2010 at 3:00 PM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>
> On 19.06.2010, at 19:55, commits at source.squeak.org wrote:
>
>> A new version of Kernel was added to project The Inbox:
>> http://source.squeak.org/inbox/Kernel-cmm.464.mcz
>>
>> ==================== Summary ====================
>>
>> Name: Kernel-cmm.464
>> Author: cmm
>> Time: 19 June 2010, 2:55:08.254 pm
>> UUID: 2f0eca0f-96b3-4435-b9f0-a7574c11c0b9
>> Ancestors: Kernel-cmm.463
>>
>> - Added Object>>#asArray.  This streamlines the use of public API's that permit a collection argument, by not requiring the user of the API to create a collection when only a single element is wanted anyway.
>>
>> =============== Diff against Kernel-cmm.463 ===============
>>
>> Item was added:
>> + ----- Method: Object>>asArray (in category 'converting') -----
>> + asArray
>> +
>> +     ^ Array with: self
>> +
>> + !
>
> Uh oh. Why not write {object} at the sending site?
>
> - Bert -
>
>
>
>