Thomas, before I reply to your comment, I have a meta-comment to make.
Your signature says "Please do not cc me. / Bitte keine Kopien per E-Mail."
which suggests that you do not want to be emailed. But your post included
an explicit "Mail-Copies-To: use...@pointedears.de" header which compliant
ne
Terry Reedy wrote:
> On 4/11/2015 3:19 PM, Thomas 'PointedEars' Lahn wrote:
>> Terry Reedy wrote:
>>> What Chris is describing is one local namespace (sheet of paper) per
>>> function *call*.
>> I *know* what he is describing: the *call* stack.
>
> My comment above was directed not at you specifi
On 4/11/2015 3:19 PM, Thomas 'PointedEars' Lahn wrote:
Terry Reedy wrote:
On 4/11/2015 12:23 PM, Thomas 'PointedEars' Lahn wrote:
Chris Angelico wrote:
The 'x' inside each function is completely separate, no matter how
many times they get called. They're usually stored on something called
a "
Terry Reedy wrote:
> On 4/11/2015 12:23 PM, Thomas 'PointedEars' Lahn wrote:
>> Chris Angelico wrote:
>>> The 'x' inside each function is completely separate, no matter how
>>> many times they get called. They're usually stored on something called
>>> a "call stack" - you put another sheet of pape
On 4/11/2015 12:23 PM, Thomas 'PointedEars' Lahn wrote:
Chris Angelico wrote:
The 'x' inside each function is completely separate, no matter how
many times they get called. They're usually stored on something called
a "call stack" - you put another sheet of paper on top of the stack
every time
Chris Angelico wrote:
> The 'x' inside each function is completely separate, no matter how
> many times they get called. They're usually stored on something called
> a "call stack" - you put another sheet of paper on top of the stack
> every time you call a function, local variables are all writte
Den lördag 11 april 2015 kl. 17:26:03 UTC+2 skrev Steven D'Aprano:
> On Sun, 12 Apr 2015 01:00 am, jonas.thornv...@gmail.com wrote:
>
> > If two functions crossreference eachother back and forth what happen with
> > the local variables.
>
> Nothing. They are local to the function that creates the
On Sun, 12 Apr 2015 01:00 am, jonas.thornv...@gmail.com wrote:
> If two functions crossreference eachother back and forth what happen with
> the local variables.
Nothing. They are local to the function that creates them.
> Will there be a new instance of function holding the variables or do the
On Sun, Apr 12, 2015 at 1:22 AM, wrote:
> Thanks i was worried, i try to make a generic base choice algorithm that
> should work for anybase, and i just realised that the bignumb add would need
> to call the bignumb subtraction and viceversa. I thought there may be
> instances but i was not su
Den lördag 11 april 2015 kl. 17:16:09 UTC+2 skrev Chris Angelico:
> On Sun, Apr 12, 2015 at 1:00 AM, wrote:
> > If two functions crossreference eachother back and forth what happen with
> > the local variables.
> >
> > Will there be a new instance of function holding the variables or do they
>
On Sun, Apr 12, 2015 at 1:00 AM, wrote:
> If two functions crossreference eachother back and forth what happen with the
> local variables.
>
> Will there be a new instance of function holding the variables or do they get
> messed up?
You mean if one function calls another, and that function ca
11 matches
Mail list logo
