Author: milo1012
Posted: Mon Aug 08, 2016 2:57 pm (GMT -6)
...
It doesn't matter. When I compile a program or DLL in C/C++ and many other languages, I use the Windows headers. These headers define MAX_PATH to 260.
So the program will have the limit set by compile time, no matter what you do in the OS later on. There is no advantage with this setting for now, except that you now *may* pass long paths to API functions w/o the infamous \\?\ prefix, but you have no guarantee for it.
So to make this have the advantage that some people think it will provide, we'd need:
_________________
TC plugins: PCREsearch and RegXtract
Posted: Mon Aug 08, 2016 2:57 pm (GMT -6)
| MVV wrote: |
| This seems to be related to native applications too |
...
| umbra wrote: |
| Actually, it's a system-wide setting. |
It doesn't matter. When I compile a program or DLL in C/C++ and many other languages, I use the Windows headers. These headers define MAX_PATH to 260.
So the program will have the limit set by compile time, no matter what you do in the OS later on. There is no advantage with this setting for now, except that you now *may* pass long paths to API functions w/o the infamous \\?\ prefix, but you have no guarantee for it.
So to make this have the advantage that some people think it will provide, we'd need:
- wait until the Windows headers (in Visual Studio, or the DDK, or the Platform SDK or whatever) is properly updated, i.e. the runtime libs may take advantage of it
- wait until MS forces this setting to be enabled all the time, otherwise it's useless when it stays optional
- not checking any more for the target OS in the application, assuming Win 10 with the mentioned update
_________________
TC plugins: PCREsearch and RegXtract