MATLAB Answers

Please help! "Error: Function definitions are not permitted in this context. "

1,659 views (last 30 days)
Agata
Agata on 16 Oct 2011
Commented: Walter Roberson on 31 Jan 2020
Hello! I'm extremely new to Matlab, and I'm working on a homework problem, and I keep coming up with an error... I've written my functions, and defined some variables to be plugged into them. I can't even call my functions, because I get the error for writing them.
This all has to be in one m-file so I cannot save the functions in different ones... I'm not sure what to do :(
function [x,y,vx,vy] = trajectory(t,v0,th0,h0,g)
x = v0 .* cos(th0) .* t;
y = h0 + (v0 .* sin(th0) .* t) - ((1./2) .* g .* (t.^2));
vx = v0 .* cos(th0);
vy = (v0 .* sin(th0)) - (g .* t);
function y = height(t,v0,th0,h0,g)
[x,y,vx,vy] = trajectory(t,v0,th0,h0,g);
%(b)
v0 = 20;
th0 = 45;
h0 = 5;
g = 9.81;
t = linspace(1,4,400);
y = height(t,v0,th0,h0,g)

  3 Comments

Mamoona Yousaf
Mamoona Yousaf on 25 Sep 2016
Function definitions are not permitted in this context. plz tell me the meaning of this error
Image Analyst
Image Analyst on 25 Sep 2016
Essentially, the code simplifies down to this:
function a = trajectory
a=10
function height
b = trajectory
c = height
There is nothing wrong with having that all in the same m-file. You can run it and won't get the error. Basically it runs trajectory, which never calls height at all. If it did, then since height calls trajectory, you could get an infinite loop because it would never stop.
What they probably did (but did not show) was to define t,v0,th0,h0,g in the same m-file, and this turned the two-function file (which is allowed) into a script+(2 functions) file which is not allowed. You can't start out an m-file with a script (like defining input arguments) and then follow up with function definitions. You can have a script only, or multiple functions, but not both in the same m-file.

Sign in to comment.

Accepted Answer

Fangjun Jiang
Fangjun Jiang on 16 Oct 2011
Edited: MathWorks Support Team on 8 Nov 2018
In MATLAB, there are two types of code files, scripts and functions. If the first executable line of your code file is a function definition like you have in the code above, then your file is a function.
If there is other MATLAB code such as variable declarations above the first function definition, then your file is a script. It sounds like you might have additional code above the code for the two functions you gave, making the file a script.
In MATLAB versions R2016a and before, you cannot have function definitions inside a script. That is what the error message is saying. To fix the problem, save each function definition in separate files, and either create a script with the additional code or simply run the additional code in the command window before calling your functions.
In MATLAB version R2016b and after, you can have function definitions in a script, and you would not see the "Error: Function definitions are not permitted in this context" error in your case. For more information about functions in scripts, see:
For more information about the difference between scripts and functions, see:

  9 Comments

Show 6 older comments
Walter Roberson
Walter Roberson on 31 Jan 2020
In r2019b it is still not permitted to define functions at the MATLAB command line, and it is still permitted to define functions inside a script (since R2016b).
When a function is defined inside a script, the name of the function must be different than the name of the script file.

Sign in to comment.

More Answers (7)

Walter Roberson
Walter Roberson on 16 Oct 2011
In addition to what Fangjun wrote:
When you are not already executing within a given file, MATLAB can only find the very first function in that file, and that first function name must be the same name as the file.
Therefore, the order of functions in the file should be that the very first one is the "driver" function (the one that sets up everything and calls the other functions to do the work), and the functions that do the internal work should be after that in the file.
If you look at the function order you have coded above, you have coded the internal routine first, and then coded a routine that calls that internal routine. You would, however, not be able to activate that second routine from the MATLAB command line.
So... what you need to do is take the line that start at %(b) through to the end of the file, and move those lines to the beginning of the file, and then you have to insert a "function" line at the very top, naming it appropriately for your assignment conditions. I can see from the code that those lines set things up and then call the internal routines, so those lines should be in the first function.

  0 Comments

Sign in to comment.


Kamil Kasic
Kamil Kasic on 28 Jan 2014
Edited: Walter Roberson on 28 Jan 2014
What is wrong here?
basic example from Matlab help:
function y = average(x)
if ~isvector(x)
error('Input must be a vector')
end
y = sum(x)/length(x);
end
function y = average(x)
|
Error: Function definitions are not permitted in this context.

  3 Comments

Walter Roberson
Walter Roberson on 28 Jan 2014
You need to store that in a file named average.m and run it from the file. You cannot create functions at the command prompt.

Sign in to comment.


Gedion Teklewolde
Gedion Teklewolde on 26 Mar 2014
Edited: Gedion Teklewolde on 26 Mar 2014
Even when it is saved in appropriate name file.m it still fails.
clc
clear
clc
%
% Newton-Raphson method
%
function [x0,err] = newraph(x0)
maxit = 100;
tol = 1.0e-6;
err = 100.0;
icount = 0;
xold =x0;
while (err > tol & icount <= maxit)
icount = icount + 1;
f = funkeval(xold);
df = dfunkeval(xold);
xnew = xold - f/df;
if (icount > 1)
err = abs((xnew - xold)/xnew);
end
fprintf(1,'icount = %i xold = %e f = %e df = %e xnew = %e err = %e \n',icount, xold, f, df, xnew, err);
xold = xnew;
end
%
x0 = xnew;
if (icount >= maxit)
% you ran out of iterations
fprintf(1,'Sorry. You did not converge in %i iterations.\n',maxit);
fprintf(1,'The final value of x was %e \n', x0);
end
function f = funkeval(x)
f = x + log(x);
function df = dfunkeval(x)
df = 1 + 1/x;

  2 Comments

Walter Roberson
Walter Roberson on 10 Jan 2016
It is not clear what was stored in which file. The 'clc' at the top of the code is not the word 'function' or 'classdef' so whatever code is in the same file as the 'clc' is part of a "script" rather than a function file. Function files must start with "function", and functions can also be defined in "classdef" files, but functions cannot be defined in scripts.

Sign in to comment.


Gireesha Obulaporam
Gireesha Obulaporam on 28 Jan 2017
I wold like to implement a Genetic Algorithm in MATLAB. So, first I tried to execute the fitness value. I entered the function name called myFitness() which is as shown below:
function y = myFitness(x)
It displays me the "Error: Function definitions are not permitted in this context".
Please suggest me how to resolve it.

  1 Comment

Walter Roberson
Walter Roberson on 28 Jan 2017
You can never use "function" at the command line.
If you are using R2016a or earlier then functions can only be defined in a file that starts with function or classdef. In R2016b you can also put functions in a script.

Sign in to comment.


Valeria Martinuzzi
Valeria Martinuzzi on 5 Jun 2017
Edited: Walter Roberson on 5 Jun 2017
This function file is giving me an error even though it seems right. It is telling me that "Function definitions are not permited on this context" This is the file:
function [s,flag] = setupSerial(s)
%Initialize the serial port communication between Arduino and MATLAB
%The input value is the COMPORT should be changed as per requirement
%We ensure that the arduino is also communication with MATLAB at this
%time. A predefined code on the Arduino acknowledges this.
%If setup is complete then the value of setup is returned as 1 else 0
flag = 1;
s= serial('COM3');
set(s,'DataBits', 8);
set(s,'StopBits', 1);
set(s,'BaudRate', 9600);
set(s,'Parity','none');
fopen(s);
a='b';
while (a~='a')
a=fread(s,1,'uchar');
end
if (a=='a')
disp('serial read');
end
fprintf(s,'%c','a');
mbox = msgbox('Serial Communication setup.'); uiwait(mbox);
fscanf(s,'%u');
end
Help please?

  1 Comment

Sign in to comment.


Nkwentie Musi
Nkwentie Musi on 11 Jul 2017
after defining my function like this Function(Zg,Zt,Zc,Yg,ZT,YT)= LineParameters(Mu,Eo,Rsu,Geom,Ncon,Ns,w) i have this error when executing the program "??? Error: File: testfinal.m Line: 41 Column: 1 Function definitions are not permitted in this context." what was i suppose to do

  1 Comment

Walter Roberson
Walter Roberson on 11 Jul 2017
Function(Zg,Zt,Zc,Yg,ZT,YT)= LineParameters(Mu,Eo,Rsu,Geom,Ncon,Ns,w)
is not valid syntax for defining a function. You need [] instead of () on the left hand side:
function [Zg, Zt, Zc, Yg, ZT, YT] = LineParameters(Mu, Eo, Rsu, Geom, Ncon, Ns, w)

Sign in to comment.


Han Wang
Han Wang on 10 Dec 2018
There is nothing wrong creating functions in .m files, but I think the mistake you are making is that you didn't put the functions at the END of you mfile. Matlab actually enforces that they have to be placed at the end of the file, in order to avoid confusions like the one you have shown in your example. I think apparently, Matlab thinks your codes following %(b) are part of the function "height", and thus it gets confused somehow.
Matlab is indeed sending you a wrong error message because it minsinterprets your whole code structure. You can try moving your main routine following %(b) to the beginning of the code. Also, it helps to attach "end" to each function you have defined.
I have encountered similar situations like yours, where I forgot to attach an "end" to a "for" loop in the main routine, and Matlab sends me the same error message as yours, apparently confused with the code structure.

  2 Comments

Walter Roberson
Walter Roberson on 10 Dec 2018
At the time the question was asked in 2011 functions could not be stored in script files .
Steven Lord
Steven Lord on 10 Dec 2018
Matlab actually enforces that they have to be placed at the end of the file, in order to avoid confusions like the one you have shown in your example.
That's not completely correct. There are three scenarios in which ending each function in a file with an end statement is required. See the "End Statements" section on this documentation page for the list of those scenarios.
You can have a function file in which none of the functions end with an end or a function file in which all of the functions end with an end. What's not allowed is for some but not all of the functions to end with an end.

Sign in to comment.

Sign in to answer this question.

Tags