Delayed evaluation of expressions [was Re: Time we switched to unicode?]

2014-03-26 Thread Steven D'Aprano
On Wed, 26 Mar 2014 00:30:21 -0400, Terry Reedy wrote: On 3/25/2014 8:12 PM, Steven D'Aprano wrote: On Tue, 25 Mar 2014 19:55:39 -0400, Terry Reedy wrote: On 3/25/2014 11:18 AM, Steven D'Aprano wrote: The thing is, we can't just create a ∑ function, because it doesn't work the way the

Re: Delayed evaluation of expressions [was Re: Time we switched to unicode?]

2014-03-26 Thread Rustom Mody
On Wednesday, March 26, 2014 9:35:53 PM UTC+5:30, Steven D'Aprano wrote: On Wed, 26 Mar 2014 00:30:21 -0400, Terry Reedy wrote: On 3/25/2014 8:12 PM, Steven D'Aprano wrote: On Tue, 25 Mar 2014 19:55:39 -0400, Terry Reedy wrote: On 3/25/2014 11:18 AM, Steven D'Aprano wrote: The thing is,

Re: Delayed evaluation of expressions [was Re: Time we switched to unicode?]

2014-03-26 Thread Rustom Mody
On Wednesday, March 26, 2014 11:02:04 PM UTC+5:30, Rustom Mody wrote: On Wednesday, March 26, 2014 9:35:53 PM UTC+5:30, Steven D'Aprano wrote: On Wed, 26 Mar 2014 00:30:21 -0400, Terry Reedy wrote: One passes an unquoted expression in code by quoting it with either lambda, paired quote

Re: Delayed evaluation of expressions [was Re: Time we switched to unicode?]

2014-03-26 Thread Chris Angelico
On Thu, Mar 27, 2014 at 4:32 AM, Rustom Mody rustompm...@gmail.com wrote: Now actual python def sumjensen(i_get, i_set,lower,upper,exp): tot = 0 i_set(lower) while i_get() = upper: tot += exp_get() i_set(i_get() + 1) return tot i=0 a=[3,4,5] i_get =

Re: Delayed evaluation of expressions

2014-03-26 Thread Marko Rauhamaa
Chris Angelico ros...@gmail.com: You prove here that Python has first-class expressions in the same way that 80x86 assembly language has garbage collection. Sure, you can implement it using the primitives you have, but that's not support. I was more reminded of STL and Boost. For example:

Re: Delayed evaluation of expressions [was Re: Time we switched to unicode?]

2014-03-26 Thread Steven D'Aprano
On Thu, 27 Mar 2014 09:24:49 +1100, Chris Angelico wrote: On Thu, Mar 27, 2014 at 4:32 AM, Rustom Mody rustompm...@gmail.com wrote: Now actual python def sumjensen(i_get, i_set,lower,upper,exp): tot = 0 i_set(lower) while i_get() = upper: tot += exp_get()

Re: Delayed evaluation of expressions [was Re: Time we switched to unicode?]

2014-03-26 Thread Terry Reedy
I agree that we have not been understanding each other. From you original post that I responded to: The thing is, we can't just create a ∑ function, because it doesn't work the way the summation operator works. The problem is that we would want syntactic support, so we could write something

Re: Delayed evaluation of expressions [was Re: Time we switched to unicode?]

2014-03-26 Thread Rustom Mody
On Thursday, March 27, 2014 5:13:21 AM UTC+5:30, Steven D'Aprano wrote: On Thu, 27 Mar 2014 09:24:49 +1100, Chris Angelico wrote: wrote: Now actual python def sumjensen(i_get, i_set,lower,upper,exp): tot = 0 i_set(lower) while i_get() = upper: tot += exp_get()

Re: Delayed evaluation of expressions [was Re: Time we switched to unicode?]

2014-03-26 Thread Steven D'Aprano
On Wed, 26 Mar 2014 20:44:17 -0400, Terry Reedy wrote: I agree that we have not been understanding each other. From you original post that I responded to: The thing is, we can't just create a ∑ function, because it doesn't work the way the summation operator works. The problem is that we

Re: Delayed evaluation of expressions

2014-03-26 Thread Rustom Mody
On Thursday, March 27, 2014 4:15:19 AM UTC+5:30, Marko Rauhamaa wrote: Chris Angelico : You prove here that Python has first-class expressions in the same way that 80x86 assembly language has garbage collection. Sure, you can implement it using the primitives you have, but that's not