Anonymous functions not acting as they should?

2 views (last 30 days)
In the following code I have two anonymous functions that work fine when the function is worked out by hand, iteration by iteration, but choke up by the fourth iteration as apre depreciates linearly to zero (not supposed to happen) and macexp levels off at 10.667 (not supposed to happen) before going directly to zero (not supposed to happen). In the version of this code which does not include any anonymous functions apre diminishes exponentially towards zero and macexp increases towards 55 (with x=4, se=.01). The code is to model the taylor series for exp(x).
x = input('Input the value of x to be approximated: ');
se = input('Input the specified error (se): ');
fprintf('\nn\t\tSeries Approx\t\tapre\n');
fmacexp=@(x,n) macexp(n)+((x^n)/factorial(n));
fapre=@(approx,n) (100*((approx(n+1)-approx(n))/approx(n+1)));
for n=1:100;
if apre<se
Yao Li
Yao Li on 9 Apr 2013
Edited: Yao Li on 9 Apr 2013
I'm not sure, but maybe it is because of factorial(n).
Since double precision numbers only have about 15 digits, the answer is only accurate for n <= 21. For larger n, the answer will have the right magnitude, and is accurate for the first 15 digits.
Sean de Wolski
Sean de Wolski on 9 Apr 2013
is the largest factorial that can be evenly represented as an integer in double precision:

Sign in to comment.

Accepted Answer

Jonathan Epperl
Jonathan Epperl on 9 Apr 2013
I think the mistake happens here:
fmacexp=@(x,n) macexp(n)+((x^n)/factorial(n));
The value of macexp is now "hardwired" with its current valued into your function famcexp, i.e. when you call macexp in your loop, macexp executes with a value of macexp=zeros(1,100) every time, not with the updated value.
What Yao commented you should also consider though, those factorials are going to get gigantic very quickly.
Yao Li
Yao Li on 9 Apr 2013
So, do you think it will be better to define the functions as a real function rather than anonymous functions since currently the two anonymous functions are defined for 100 times
Teja Muppirala
Teja Muppirala on 9 Apr 2013
For something this simple, it doesn't really matter, it's just a matter of milliseconds anyways. If efficiency is really an issue, then certainly you don't want to be redefining function handles all the time.
I would have probably written it like this outside the loop just once:
fmacexp=@(x,n) ((x^n)/factorial(n));
And then inside the loop do
macexp(n+1) = macexp(n+1) + fmacexp(x,n)

Sign in to comment.

More Answers (0)


Find more on Loops and Conditional Statements in Help Center and File Exchange

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!