Matlab modifies my m-file timestamps?

The way I use often use Matlab is to have a script m-file open in emacs on a linux workstation, but run the script on a windows machine where Matlab is installed (file is on a network share). Clearly this is non-ideal, but I have to live with it.

Anyway, when I run my Matlab script, then want to make changes in emacs, I find that I get complaints about the file having been modified on disk. Matlab appears to modify the timestamp of the file when you run the script (and then resets it afterwards?). This isn't a problem except when you are making many changes to the script and running it often... but that's usually the case in my situation.

Any thoughts on how to get Matlab to stop doing this? Or ideas as to why I might be confused here?

Thanks!

[Walter Roberson]

Does this happen to exactly the files you put breakpoints in?

[Daniel Shub]

I am willing to try and recreate this problem, but need more details/clarification. The file is stored on one machine, open for editing on a Linux machine, and running on a windows machine. How have you mounted the filesystem in Linux and Windows?