Because it's additional development effort. I'm 95% sure there's no other reason.gigaman wrote:Maybe I'm missing something obvious - but why not use dynamic strings (i.e. with a size allocated according to current content length) - especially if memory usage should be an issue?
Since most paths are short anyway (shorter than 260 characters), it would save memory almost always...
work with long (actually very long) file/dir names.
Moderators: Hacker, petermad, Stefan2, white
Storing *MANY* paths/files
Maybe the best solution to store so many path/files is to create a database exactly like the directory structure on the disk (and consequently manage it in the proper way)
Maybe...
Maybe...
/-\ /\/\ /\/\ /-\ /\/\ /\/\ /-\ T /-\
Isn't that what treeinfo.wc is ?create a database exactly like the directory structure on the disk
License #524 (1994)
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14
TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14
TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar