Well... ok... if you want to see if files with different names are the same, you do need to deal with OS issues.
On a unix-like system, you can check if the filesystem and inode number are the same. (And if you do not want to deal with file systems, you can use directory name as a rough approximation - though that will be defeated sometimes by symbolic links.) On a windows system, I think one analogous mechanism involves using the GetShortPathName winapi call. Another involves using GetFileInformationByHandle and then checking something like (2^32)#. nFileIndexHigh, nFileIndexLow As for the command line routines failing - that might mean that that some winapi call won't work. But that should not prevent editing - that should only prevent duplicate detection. But is file name case folding the only thing that's different here? Thanks, -- Raul On Wed, Jan 31, 2018 at 11:48 PM, chris burke <[email protected]> wrote: >> It seems to me that, as long as you do not manipulate the case of > filenames, it should not matter whether the OS is case sensitive or not. > > Well, since Microsoft's own DOS commands do not work properly with the > Google Drive folder, then it surely does matter. > > And for example in the Qt IDE, if you open file mywork.ijs and save as > MyWork.ijs, is this the same file or a new one? Is the same tab used in the > editor or a new tab? The IDE keeps track of changes to scripts for later > comparison and possible reversion, so are the changes to mywork.ijs the > same as for MyWork.ijs? If a file open in the editor is changed by another > program, then the IDE will prompt for reload, but what happens if changes > are made to a file with a differently capitalized name? There are several > issues of this nature, that were never a problem before. > > > On Wed, Jan 31, 2018 at 5:06 PM, Raul Miller <[email protected]> wrote: > >> It seems to me that, as long as you do not manipulate the case of >> filenames, it should not matter whether the OS is case sensitive or >> not. The OS gives you a character literal which identifies a file, >> which you can use to identify that file. A different character literal >> may or may not identify the same file (and the details of that issue >> will depend on the OS - file links and case folding being two >> potentially relevant issues here). >> >> Thanks, >> >> -- >> Raul >> >> >> On Wed, Jan 31, 2018 at 6:32 PM, chris burke <[email protected]> wrote: >> > It seems the problem is that Google Drive Stream is case-sensitive. >> > >> > Hard to believe and troublesome to support, since we would have to treat >> > those directories differently from the rest of the system. >> > ---------------------------------------------------------------------- >> > For information about J forums see http://www.jsoftware.com/forums.htm >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
