Re: OT: C vs Python terminology

2013-06-16 Thread Dave Angel
On 06/16/2013 11:02 AM, Andreas Perstinger wrote: On 16.06.2013 14:55, Dave Angel wrote: On 06/16/2013 07:22 AM, Andreas Perstinger wrote: But it doesn't. It binds b to the same object to which a is currently bound. Are you aware that Denis was talking about the behaviour of C in the abov

Re: OT: C vs Python terminology

2013-06-16 Thread Andreas Perstinger
On 16.06.2013 14:55, Dave Angel wrote: On 06/16/2013 07:22 AM, Andreas Perstinger wrote: On 16.06.2013 08:32, Denis McMahon wrote: C: ^ int a, b; b = 6; a = b; In C, this places the numeric value 6 into the memory location identified ^ by the variable "b", so far s

Re: OT: C vs Python terminology

2013-06-16 Thread Dave Angel
On 06/16/2013 07:22 AM, Andreas Perstinger wrote: On 16.06.2013 08:32, Denis McMahon wrote: C: int a, b; b = 6; a = b; In C, this places the numeric value 6 into the memory location identified by the variable "b", so far so good. then copies the value from the location pointed to by "b" in

OT: C vs Python terminology (was: A certainl part of an if() structure never gets executed)

2013-06-16 Thread Andreas Perstinger
On 16.06.2013 08:32, Denis McMahon wrote: C: int a, b; b = 6; a = b; In C, this places the numeric value 6 into the memory location identified by the variable "b", so far so good. then copies the value from the location pointed to by "b" into the location pointed to by "a". Wrong. Neither