[Octave-bug-tracker] [bug #53917] Incorrect warning: time stamp for 'filename' is in the future

[Ian McCallion]

URL:
  <http://savannah.gnu.org/bugs/?53917>

                 Summary: Incorrect warning: time stamp for 'filename' is in
the future
                 Project: GNU Octave
            Submitted by: ianmcc
            Submitted on: Tue 15 May 2018 08:18:15 PM UTC
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.4.0
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

The script below shows an unwanted interaction between using TZ for the
purposes of the application and Octave's inappropriate dependency on the
current value of of TZ in monitoring the Octave path for changed files.
(Caveat. I'm on windows) 
Before launching this script, create a valid do-nothing function called
dummy.m. An empty file does not show the problem 

system('touch dummy.m') % make sure timestamp is NOW 
setenv('TZ', 'UTC0'); % !!!!! USE A TIMEZONE THAT IS WESTERLY FOR YOUR
LOCATION !!!! 
mktime(localtime(1)); % This is necessary only in Octave for Windows to bypass
a bug in the posix layer which will be reported separately 
pause (2); % Does not always happen without the pause 
% the next command should report that the file has a timestamp in the future 
dummy 
setenv('TZ', '') 
mktime(localtime(1)); 


I am using Windows 10. The file is on a hard disk formatted NTFS. The touch
command sets the filetime correctly to the current time yet the output of the
script is:

>> filechangedbug
ans = 0
warning: time stamp for 'C:\Users\Ian\documents\backed\HawkEarGit\dummy.m' is
in the future
warning: called from
    filechangedbug at line 8 column 1
dummy





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53917>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/