[think-dev] RE: collection interfaces

[<stephane.seyvoz@xxxxxxxxxxxxxxxxxx>]

Hi Olivier,

I didn't quite get the last point about not being possible to iterate over 
the collection... Is it linked to the "-1", "-2",... "-n" suffix ?
And I don't catch the thing about the index being an integer (which seems 
quite normal to me :) ) related to this iteration.

Bonus : In the dynamic non-optimized version, is there a way to know the size 
of the collection ? Thanks in advance :)

Stéphane


-----Message d'origine-----
De : Olivier Lobry [mailto:olivier.lobry@xxxxxxx] 
Envoyé : vendredi 19 juin 2009 15:48
À : think-users@xxxxxxx; think-dev@xxxxxxx
Objet : [think-dev] collection interfaces

Hi all,

I'm about to add support for collection client interfaces with a fixed and 
predefined size:
  - to declare a collection interface 'foo' of size 3: requires fooType as 
foo[3]
  - to binds a collection interface 'foo', index 1: binds comp.foo[1] to 
srvItf // note that itf index starts from 0, so valid values are in this case 
: 0, 1 or 2
  - to call a method 'bar' of a collection interface 'foo', index 1:  
foo_bar[1](...)
  - elements of a client collection interface 'foo' are named "foo-1", 
"foo-2", ... in the binding controller

With the following restrictions:
  - bindings of a collection interface will be optimize only if
**all** bindings from this interface are static
  - if all bindings are static, the index of a call must be a integer (not 
possible to iterate over the collection)

The code is in nuptse/branches/collection-itfs and has been tested against 
nuptse & kortex examples

Do you have any comments or suggestions before I merge it to the trunk ?

Regards,

Olivier