Re: Long, long file names?
From: Maarten Wiltink (maarten_at_kittensandcats.net)
Date: 11/03/04
- Next message: Maarten Wiltink: "Re: Structured Exception Handling (was: Try Finally...)"
- Previous message: Maarten Wiltink: "Re: Been a slice..."
- In reply to: Supply and Demand: "Long, long file names?"
- Next in thread: Supply and Demand: "Re: Long, long file names?"
- Reply: Supply and Demand: "Re: Long, long file names?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 3 Nov 2004 20:13:31 +0100
"Supply and Demand" <ask_me_for_it@and_I_might_tell.you> wrote in message
news:cmb4qc$qi$1@news.island.liu.se...
[...]
> MSDN says that the file name itself can be 255
> characters long if the unicode versions of some
> functions are used.
Yes, notably CreateFileW, I'd guess. This would be the
bit that also says "and prepend "\\?\" to the path."?
And "For more information, see Naming a File."?
> [...] MSDN also says that Windows always
> stores file names in unicode.
On NTFS, probably always. On FAT, long filenames, yes.
Short filenames, no (that being the backwards compatible
part).
> This means that CreateFileW() must be used instead
> of AssignFile()/Rewrite()?
Ah, there's your CreateFileW. Yes. If you want raw access
to Windows features, you forego the more or less portable
Pascal RTL.
Groetjes,
Maarten Wiltink
- Next message: Maarten Wiltink: "Re: Structured Exception Handling (was: Try Finally...)"
- Previous message: Maarten Wiltink: "Re: Been a slice..."
- In reply to: Supply and Demand: "Long, long file names?"
- Next in thread: Supply and Demand: "Re: Long, long file names?"
- Reply: Supply and Demand: "Re: Long, long file names?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
