I am thinking of writing a path_name_class that would be easily adaptable to any file system, but I have run in this difficulty: it appears that some file systems allow ALL unicode except null characters in their directory entry (this is the case for example for exfat and many others (as reported by the wikipedia entry "comparison of file systems")).
So here is a mystery I have not been able to solve even after googling a lot: how can you possibly represent a path in those circumstances as a wchar array ?
Is NULL used as a the component separator for those file systems with a path length becoming necessary so that you could for example specify it this way easily this way in a wstring? Or is the path ending specified with double NULL?
trantran
0
Junior Poster in Training
Recommended Answers
Jump to Posthave you looked at boost file system fuctions? Boost may have already solved your problem for you.
Microsoft has not released the official exFAT file system specification, and a restrictive license from Microsoft is required in order to make and distribute exFAT implementations. Microsoft also asserts patents on exFAT …
Jump to PostSo what's the problem with that? NULL is just a string terminating character, not part of a file name in any file system that I know of. If you have a file that contains a filename that is terminated with a NULL byte then all your program has to do …
All 8 Replies
Ancient Dragon
5,243
Achieved Level 70
Team Colleague
Featured Poster
trantran
0
Junior Poster in Training
Ancient Dragon
5,243
Achieved Level 70
Team Colleague
Featured Poster
trantran
0
Junior Poster in Training
Ancient Dragon
5,243
Achieved Level 70
Team Colleague
Featured Poster
trantran
0
Junior Poster in Training
Ancient Dragon
5,243
Achieved Level 70
Team Colleague
Featured Poster
trantran
0
Junior Poster in Training
Be a part of the DaniWeb community
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.