[Octave-bug-tracker] [bug #60493] ignore_function_time_stamp none has no effect

[Rik]

Follow-up Comment #4, bug #60493 (project octave):

Also, note that the original Stack Overflow example was done on Windows.  Time
stamps on that platform can be horrendously crude (for example, everything
within 100 milliseconds is tagged with the same timestamp).  That lack of
precision is not Octave's fault.  Running interactively helps mitigate this
because each change to an m-file is done after the user copy and pastes the
new code and then hits return.  This operation typically takes at least 1
second so there is no issue with the imprecise timestamps.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60493>

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