It appears that in the array addon, the "length" accessors have been replaced by "size". It's indeed a good idea to have all containers use the same syntax. However, why not keep the old length accessor as well? Otherwise all existing code referring to the length property is broken.

I suggest that you simply keep both, to maintain compatibility:

	// Register virtual properties
	r = engine->RegisterObjectMethod("array<T>", "uint get_length() const", asMETHOD(CScriptArray, GetSize), asCALL_THISCALL); assert( r >= 0 );
	r = engine->RegisterObjectMethod("array<T>", "void set_length(uint)", asMETHODPR(CScriptArray, Resize, (asUINT), void), asCALL_THISCALL); assert( r >= 0 );
	r = engine->RegisterObjectMethod("array<T>", "uint get_size() const", asMETHOD(CScriptArray, GetSize), asCALL_THISCALL); assert( r >= 0 );
	r = engine->RegisterObjectMethod("array<T>", "void set_size(uint)", asMETHODPR(CScriptArray, Resize, (asUINT), void), asCALL_THISCALL); assert( r >= 0 );

What do you think?

By the way, this also applies to the stdstring addon (for which length actually seems more appropriate to me than size anyway ? ).

So you mean that we have to choose between the length() function and the get-length accessor then?

I have tried the patch suggested above and it works fine so I am not sure to understand.

Thanks, it makes sense. I guess I'll have to get rid of the length() method then, as I definitely do not need it! Why this choise of keeping the length function and changing the property to "size" by the way? It looks like it will also break for people using the stl style.

Thanks! This is more than great!