Steven Schveighoffer wrote:
> I don't expect this to be a huge problem.  Will people who more likely
> destroy an object with:
> 
> clear(obj);
> 
> or
> 
> obj.clear();
> 
> ?  To me, the first looks like you are doing an operation to the object,
> where the second looks like you are having the object do an operation.
> 
> UFC is going to cause lots of these little corner cases.  Another I can
> think of is global properties.  with @property foo(int x), do you call
> this as foo = 1; or 1.foo?
> 
        I believe this becomes a problem when you have *both* a free
standing function (to destroy the container) and a method (to empty
it). And yes, this will crop up a lot with UFC.

                Jerome
-- 
mailto:[email protected]
http://jeberger.free.fr
Jabber: [email protected]

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to