currently, va2modspec('vafile.va') will quietly overwrite any vafile.m that exists in the current directory.
I know this behaviour is documented - but this is a poor choice for a self-styled "UI", especially given how easy it is to do the right thing - which is to tell the user that vafile.m exists and will be overwritten, and offer a choice to go ahead or abort.
currently, va2modspec('vafile.va') will quietly overwrite any vafile.m that exists in the current directory.
I know this behaviour is documented - but this is a poor choice for a self-styled "UI", especially given how easy it is to do the right thing - which is to tell the user that vafile.m exists and will be overwritten, and offer a choice to go ahead or abort.