31 Oct
2005
31 Oct
'05
11:38 p.m.
Alex Villacís Lasso <a_villacis(a)palosanto.com> writes:
Sorry to disagree, but I have seen this behavior (fully qualified name in argv[0]) since MS-DOS and Windows 3.1. Even some old C tutorial books mention it in passing. I have also replicated this behavior from the command line (COMMAND.COM) in MS-Windows 98 in a DOS box, without using Explorer. My sample app prints out the argv[] array and it consistenly shows a fully qualified path to the executable in argv[0], even when run from a DOS box.
It's OK to change argv[0] when started from a Unix shell, but not when started from another Windows process. Your patch does it in all cases, which is not correct. -- Alexandre Julliard julliard(a)winehq.org