Path: news.mathworks.com!not-for-mail
From: <HIDDEN>
Newsgroups: comp.soft-sys.matlab
Subject: M files must be run twice for changes to take effect on linux system
Date: Thu, 20 Sep 2007 20:28:24 +0000 (UTC)
Organization: UBC
Lines: 13
Message-ID: <fcul58$kac$1@fred.mathworks.com>
Reply-To: <HIDDEN>
NNTP-Posting-Host: webapp-05-blr.mathworks.com
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: fred.mathworks.com 1190320104 20812 172.30.248.35 (20 Sep 2007 20:28:24 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Thu, 20 Sep 2007 20:28:24 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 162893
Xref: news.mathworks.com comp.soft-sys.matlab:429497



Weird question. Running Matlab r2006a on  a 64bit linux
system I ran into the following. Whenever I change something
in an m-file, the first time I then call it from the command
window it will not include the changes just made. I will
need to run it again, to have it updated. 

This is not only a hassle but also very problematic when
checking for bugs, or developing code in general. I never
had this before (I've ran various Matlab versions on both
windows, linux and unix over the last years) and I'm pretty
much clueless as to where this might be coming from.

Thanks for any input!