[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Wind
From: |
anonymous |
Subject: |
[Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows |
Date: |
Tue, 5 Jan 2021 00:47:05 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 5.1; rv:68.9) Gecko/20100101 Goanna/4.6 Firefox/68.9 Mypal/28.14.2 |
Follow-up Comment #35, bug #59706 (project octave):
"I can't tell from comment #32 whether Octave already does this, or only the
first time the path is built."
I called 'find_function' twice with two non-cached names. The list of API
functions that are called is attached. Line 781 is where the second
'find_function' begins. The same process as noted in comment #32 is repeated
for both functions.
"If we want to be fancy, when we detect a directory exists we need to populate
the cache with the m-files that it contains."
It may require the path folders to be monitored for any changes in their
contents such as addition or deletion of .m, .oct or .mex files or private
directories. Windows has such a capability that is discussed under Obtaining
Directory Change Notifications [1].
[1]
https://docs.microsoft.com/en-us/windows/win32/fileio/obtaining-directory-change-notifications
(file #50655)
_______________________________________________________
Additional Item Attachment:
File name: callstack-611-find_function_called_twice.cc Size:130 KB
<https://file.savannah.gnu.org/file/callstack-611-find_function_called_twice.cc?file_id=50655>
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?59706>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, anonymous, 2021/01/03
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, Markus Mützel, 2021/01/03
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, anonymous, 2021/01/03
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, Markus Mützel, 2021/01/04
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, anonymous, 2021/01/04
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, Rik, 2021/01/04
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, anonymous, 2021/01/05
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows,
anonymous <=
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, Rik, 2021/01/13
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, Markus Mützel, 2021/01/14
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, anonymous, 2021/01/14
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, anonymous, 2021/01/14
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, Markus Mützel, 2021/01/14
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, Rik, 2021/01/14
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, anonymous, 2021/01/15
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, Markus Mützel, 2021/01/15
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, anonymous, 2021/01/15
- [Octave-bug-tracker] [bug #59706] Avoid "canonicalize_file_name" on Windows, Markus Mützel, 2021/01/15