Close diary file on Error
11 visualizaciones (últimos 30 días)
Mostrar comentarios más antiguos
gire
el 20 de Jul. de 2012
Comentada: Tria Technologies
el 29 de En. de 2025
Hi, I am using the diary function to log my application output. Something like
diary(path_to_logfile)
% all my code with output to the console, matrices written to desk, etc
diary off
When the code fails, the diary is not closed. One option would be to wrap all the code on a try-catch statement and close it on the catch.
Is there another way to avoid the diary being "open" when the app fails?
0 comentarios
Respuesta aceptada
Jan
el 20 de Jul. de 2012
TRY-CATCH is really the best solution:
diary(path_to_logfile)
try
% all my code with output to the console, matrices written to desk, etc
catch ME
fprintf(1, 'ERROR:\n%s\n', ME.message);
end
diary off
This is clean an efficient, and you could insert other code for cleanup also, e.g. fclose('all').
Más respuestas (2)
Andrew Janke
el 31 de En. de 2020
The onCleanup function is what you want in modern Matlab. No try/catch to ugly up your code, and it's robust even against a dbquit.
function my_function
diary(path_to_logfile)
RAII.diary = onCleanup(@() diary('off'))
% ... now do whatever, and don't worry about closing the diary; it'll
% be automatically closed whenever this function returns for any reason...
end
2 comentarios
Tria Technologies
el 29 de En. de 2025
Upvoting the use of onCleanup I recently discovered this and it has added better predictability to functions. Of course, classes have built in delete() methods for doing the same.
Ver también
Categorías
Más información sobre Scope Variables and Generate Names en Help Center y File Exchange.
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!