> Last choice is to follow Microsoft's strategy and disable access to
> folders with pathnames longer than MAX_PATH. FO dialog and Windows Explorer
> show error message "Can't access this folder. Path is too long." when you
> try to enter such directories.
Know you dont like it but if there are not really good reasons I would stick with this.
There are many structures like SHFILEINFO where a element in a structure is limited
to MAX_PATH. We can't change this without breaking binary compatibility.
Second point: buffers in windows applications are often allocated on the stack. If
we give paths longer than MAX_PATH back to such a application we will get a buffer
overrun.
If you need to handle longer paths in a winelib application, change MAX_PATH to a
bigger
value but don't load a native dll then...
Any workround I can imagine breaks if it comes to such functions so I would leave
it like it is and block paths>MAX_PATH as early as possible.
Ciao
Juergen
---
[EMAIL PROTECTED]
... from sunny Berlin
