auto, var, raii,scope, banana

[Sean Kelly]

Tommie Gannert wrote:
>>>> I don't see the utility in static opCall, I say abolish/remove it. 
>>>> Non-static opCall on the other hand can be quite useful.
>>>
>>> But there is utility in static opCall in structs; having them there 
>>> but not in classes doesn't sound to cool/consistent..
>>
>> The only utility in static opCall is to emulate a constructor. Why not 
>> replace them with a constructor (ie. rename "static opCall" to 
>> "this"). Then, remove static opCall altogether.
> 
> I haven't been following this, but static opCall sounds an awful lot 
> like a function call to a function with static variables... I must join 
> the "who would want such a thing"-side.

Support for static operator functions can be useful for refactoring code 
in some cases, or for some odd template uses.  I don't use the feature 
very often, but it's nice to have available.


Sean