comp.lang.idl-pvwave archive: archive » Bug or desired behavior in lambda functions?

Home » Public Forums » archive » Bug or desired behavior in lambda functions?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Bug or desired behavior in lambda functions? [message #91136]

Mon, 08 June 2015 10:34

penteado
Messages: 866
Registered: February 2018

Senior Member
Administrator

Hello,

Despite what the documentation might suggest, and one might expect, it seems there is no way to use string variables to make lambda functions.

If I try to make a lambda function with the code inside lambda(), all is well:

IDL> l=lambda('x: x^2')
IDL> l(2)
4

However, if I put the same code in a string and pass it to lambda, it does not accept the code:

IDL> expr='x: x^2'
IDL> l=lambda(expr)
% LAMBDA: Code must be of the form "arg1,arg2,... : statement"

I expect this is caused by IDL parser's special behavior when it encounters lambda(), which is what allows this

IDL> l=lambda(x: x^2)

So I think when I put a variable name inside the lambda() call, the parser thinks is a string literal, and tries to parse the variable name as code.

Is this intended behavior, or a bug?

Paulo

Report message to a moderator

[Message index]

		Bug or desired behavior in lambda functions? By: penteado on Mon, 08 June 2015 10:34
		Re: Bug or desired behavior in lambda functions? By: penteado on Mon, 08 June 2015 13:31
		Re: Bug or desired behavior in lambda functions? By: PMallas on Tue, 09 June 2015 06:09
		Re: Bug or desired behavior in lambda functions? By: penteado on Tue, 09 June 2015 08:42

Previous Topic:	Identify whether value is integer in IF statement
Next Topic:	Multiple Processing

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 16:12:03 PDT 2025

Total time taken to generate the page: 0.00242 seconds