Semi colons aren't suppressing output

I have this as part of my code, i try to suppress as the output takes a while to finish, but semi colons aren't working

SECTIONS={'Joints','Model','Segments','Trajectories'};  % the looked for data sections
ich=find(cellfun(@ischar,G(:,1)));          % the records that have char() data first column
isec=ich(contains(G(ich,1),SECTIONS));      % the locations of each section beginning
isec=[isec;size(G,1)+2];                    % add last line for indexing sections first:last lines
for i=1:numel(SECTIONS);
  vn=string(G(isec(i)+3,:));
  in=find(ismissing(vn));
  vn(in)="Var"+in;
  cmd=sprintf('t%s=cell2table(G(isec(%d)+5:isec(%d)-2,:))',SECTIONS{i},i,i+1);
  eval(cmd);
end

[Stephen23]

"but semi colons aren't working"

You forgot to put a semi-colon at the end of the text that you EVAL.

Note that using a structure or cell array would be simpler, more reliable, and more efficient than using EVAL:

https://www.mathworks.com/matlabcentral/answers/304528-tutorial-why-variables-should-not-be-named-dynamically-eval

[Jak]

thank you for your reply

where do you mean? There is a semi colon on the end of each line, or do i need it elsewhere?

[Stephen23]

"where do you mean?"

At the end of the text that you EVAL: is there a semi-colon? Answer: no.

"There is a semi colon on the end of each line"

Sure, but that is not the problem.

"or do i need it elsewhere?"

Yes, at the end of the text that you provide to EVAL.

Note that using a structure or cell array would be simpler, more reliable, and more efficient than using EVAL:

https://www.mathworks.com/matlabcentral/answers/304528-tutorial-why-variables-should-not-be-named-dynamically-eval

[Peter Perkins]

I mean, the bigger thing is, "don't do that". You are creating vars in your workspace using sprintf and eval. There are lots of posts about why that is not a good thing.

That whole line of code, with the exception of the LHS of the assignment, can be written as literal code, using i as a subscript. And if you assign to a field of a scalar struct as mydata.(['t' SECTIONS{i}]), you can get rid of the eval.

Answer 1

[Jan]

The problemis here:

cmd =sprintf('t%s=cell2table(G(isec(%d)+5:isec(%d)-2,:));', SECTIONS{i}, i, i+1);
%                                                       ^ insterted

A much better way to store the data is:

t.(SECTIONS{i}) = cell2table(G(isec(i)+5:isec(i+1)-2,:));

See: TUTORIAL: Why and how to avoid Eval .

Creating variables dynamically impedes the processing speed, because the JIT acceleration cannot know in advance, which variables are existing and which are not. Then instead of replacing calls of variables by fast pointers, Matlab search each variable in a lookup table - even the ones to concerned by the EvAL command. This can slow down the code by a factor of 100.

In addition EVALing variables makes it hard to impossible to debug your code. You see, that a forgotton semivolon is hard to find already. Compare the readability of the two lines above.