ref returns and properties

[John Reimer]

Hello dsimcha,

> == Quote from Daniel Keep (daniel.keep.lists at gmail.com)'s article
> 
>> Sean Kelly wrote:
>> 
>>> Daniel Keep wrote:
>>> 
>>>> Andrei Alexandrescu wrote:
>>>> 
>>>>> Denis Koroskin wrote:
>>>>> 
>>>>>> [snip]
>>>>>> 
>>>>>> get/set/free?
>>>>>> 
>>>>> With these you can't move a resource inside the property.
>>>>> 
>>>>> Andrei
>>>>> 
>>>> Python has an overload for removing properties.  In all my years of
>>>> using Python, I've *NEVER* once had a use for it, or even worked
>>>> out why I'd want to use it.
>>>> 
>>>> I'm not saying we shouldn't be able to do this, I just can't see
>>>> the need for move/remove for properties; where would this be
>>>> useful?
>>>> 
>>> Does Python have complex value types?
>>> 
>>> Sean
>>> 
>> You mean these?
>> 
>>>>> (1+2j) * (2+3j)
>>>>> 
>> (-4+7j)
>> Don't ask me why they used 'j' instead of 'i'.  :P
>> If you mean aggregate types that have value semantics, then no.
>> -- Daniel
> Using j instead of i is pretty common in electrical engineering
> circles.  i means current when dealing with circuits, and complex
> numbers are used all over the place to make the math easier when doing
> circuit stuff, so by convention j is used instead of i to denote
> imaginary numbers.
> 



Right, the 'j' notation is used in the representation of phasors in ac circuit 
analysis.  If I remember correctly, 'i' , usually represented as a function 
of time, is the changing current (like in a sinusoidal waveform)... and 'I' 
is the instantaneous current.  I used to do a lot of phasor calculation practice. 
:-P


-JJR