Clearing workspace variables while in a loop.

9 次查看（过去 30 天）

Kyle Reagan 2016-12-4

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/315281-clearing-workspace-variables-while-in-a-loop

评论： Walter Roberson 2016-12-5

I have a while loop that contains a menu and some options for the user to input. One of them is to delete the workspace variables. However, whenever I clear the workspace it doesn't actually clear until the while loop stops (this occurs when they exit the program).

% case 3 
    % Clear data from memory
    clearvars -except continueprogram % 
    % This clears the entire workspace, while allowing the 
    % program to continue running.
    %             
    clc;
    fprintf('The memory is cleared. Press a key to continue. \n')
    pause;

3 个评论
显示 1更早的评论隐藏 1更早的评论

Kyle Reagan 2016-12-4

The loop is a data analysis tool for an uploaded file. It does things like plot histograms, linear regression, etc. One of the options on my menu is "Clear All" so that the user can clear all the file data, and then upload a new file without ever having to exit from the program.

Stephen23 2016-12-5

Clearing variables in a loop seems like an inefficient way to write code. Either the variables are re-allocated in each iteration (in which case clearing them serves no purpose) or new variables are created on each iteration (in which case the code is going to be buggy and slow no matter what).

Clearing variables is slow. Code of this complexity should be written as a function (and not a script), in which case it is totally irrelevant to the end user what variables exist in the function workspace.

请先登录，再进行评论。

请先登录，再回答此问题。

回答（1 个）

Walter Roberson 2016-12-4

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/315281-clearing-workspace-variables-while-in-a-loop#answer_245867

How can you tell that the workspace is not actually cleared?

If you are using the Workspace Browser then you need to know that (at least in recent versions) the Workspace Browser is not updated until you stop in the debugger or use keyboard() or control returns to the command line.