Conventional / "best practices" location for personal functions
3 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
Is there a conventional / standard / "best practices" location for parking self-developed functions, such that they are globally available from the command prompt (i.e. independent of current working directory)? I initially thought about $MATLABROOT/toolbox/local, but that contains exclusively TMW-provided scripts and text files. Moreover, as explained by John D'Errico in this old thread, there are potential issues with path caching at startup for anything placed inside $MATLABROOT.
(To be clear, I'm interested in where, rather than how. Either path or pathtool can be used to do the latter.)
5 Kommentare
Stephen23
am 22 Mai 2020
Bearbeitet: Stephen23
am 22 Mai 2020
@AMM: you should not add/remove/edit files within any application's installation directories. This is not just because of function caching issues (i.e. something specific to MATLAB), but because it is inherently a bad idea to alter anything in the installation directory of any application, even in locations that you think are benign, e.g. MATLAB's toolboxes.
https://www.mathworks.com/matlabcentral/answers/222839-how-to-use-functions-from-private-directories
There be dragons!
Akzeptierte Antwort
Image Analyst
am 22 Mai 2020
I do just like dpb says. The Mathworks told me to have a work folder, and all my various 200+ projects have subfolders under work. In addition, I have one folder there called Utilities that has a bunch of useful functions that I use all the time in other programs. I set a path to it in my startup.m file.
Weitere Antworten (0)
Siehe auch
Kategorien
Mehr zu Adding custom doc finden Sie in Help Center und File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!