From: SourceForge.net <no...@so...> - 2005-05-17 09:15:12
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3155265 By: keithmarshall Your problem has nothing to do with slashes vs. backslashes in path names. It seems to be a popular misconception among Win32 developers, that backslashes are required; in fact *all* versions of Windows, and even MS-DOS since v2.x before them, *natively* support the use of *both* slashes and backslashes. It is only command line tools designed for Microsoft's command interpreters, and indeed these interpreters themselves, which, in trying to emulate Unix and CP/M conventions simultaneously, get confused by slashes. The problem you are observing is more typical of an attempt to access memory via an unintialised pointer. It's a bug in *your* code, and has nothing to do with path name semantics. You will have to debug it. Regards, Keith. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=286529 |