On 3/8/07, Jorge Luis Zapata Muga <[EMAIL PROTECTED]> wrote: > > basically it was on the eet TODO, both group types were already > defined but weren't implemented. I was looking for any of them for a > project i'm coding on parallel. If your question is why are both > EET_G_ARRAY and EET_G_VAR_ARRAY defined on eet, i guess it will handle > more data types from the client side. (of course i'm avoiding the > benefits of a variable length array from a programmer point of view).
I guess I should have been more clear on my question. What I meant is why are two different types necessary? When encoded in the eet, how is there any difference between a variable array and a static array? Can't the number of elements be calculated in the size of the encoded region if you know the size of the individual elements? > Note that if you want to encode a variable number of elements of an > array (without the EET_G_VAR_ARRAY) you must say how many to the api > before encoding, using variable arrays the encoding handle's it by > itself (of course you will need the counter offset to know how many > elements are in there). With this you can define the descriptor at the > beginning and don't care about the length or when to encode. Is this so that you can do a sizeof(my_array) on a fixed size array rather than passing the number of elements or is the counter offset defining an offset within a struct that points to a counter for the number of elements in the array? Thanks for clarifying. Nathan ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
