I find it so interesting, that even a 64 bit OS, still uses that API,
limited to 260 (249 in fact) characters for directories and files.
FindFirstFileExW tells us about the \\?\ prefix, to overcome that limit, BUT
the WIN32_FIND_DATA structure, contains just 260 characters for the
cFilename section! :)
Is there an elegant alternate way to recursively have no MAX_PATH limit
while finding the directories
ps: My solution needs to be generic and I don't want to sell 'no cannot be
done' the customer.
Re: EOF location? ... Certain application programs may still recognize Ctrl-Z and ... I'm not sure how we got on the subject of what is or is not part of an API.... you are correct: the common file and string handling routines do not care about the EOF char -- it is divorced from the notion of end-of-file). ... My last two paragraphs were off-hand remarks meant to convey "such characters may be present, but the programmer only needs to care about them if they need to care about them". ... (comp.lang.cobol)
Re: Feedback wanted on programming introduction (Python in Windows) ... handle files or folders with paths greater than some 260 characters, is unable to handle filenames that differ only in case and are in the same directory, and is unable to e.g. delete a folder called "con" -- although such files & folders can very easily be created. ... For NTFS it's 32K or 64K wide characters,... But what's important is that that's also the API level limit.... (comp.lang.python)
Re: Max length of file name? ... I should have said "characters"....CreateFile function:... If the file is stored in an NTFS file system then: ... If the file is accessed using an ANSI API,... (microsoft.public.vc.mfc)
Re: Decimal Strings and ANSI X3.9 ... Do you try to preserve superfluous elements and the decimal point position when editing DS values? ... If you use the string...API you will see the sequence of characters as contained in the dataset ... (comp.protocols.dicom)
