Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!nuzba.szn.dk!pnx.dk!fu-berlin.de!uni-berlin.de!news.dfncis.de!not-for-mail From: =?UTF-8?B?U3ZlbiBLw7ZobGVy?= Newsgroups: comp.lang.java.programmer Subject: Re: exec problem is JDK 1.7.0_21 Date: Sun, 21 Apr 2013 23:12:22 +0300 Lines: 21 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: news.dfncis.de uT7mVpX+AlUelsrUlMg4lwti2VfgD362M1GCiLAxpQ/LalT/EJ8UXMSX+O Cancel-Lock: sha1:kTB9a2E8OM4MJ1VLRu1Ijzw9KJw= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 In-Reply-To: Xref: csiph.com comp.lang.java.programmer:23556 Am 21.04.2013 14:08, schrieb Martin Gregorie: > It says *some* operating systems. No mention of Windows. True, from which you conclude, that the following does not apply to Windows. That the documentation is dangerously vague - but that's another issue. > It also says > "there are operating systems where programs are expected to tokenize > command line strings themselves" which is not Windows IME - the C, C++ > and Java CLI programming interface is the same for these in UNIX, Linux, > OS-9 and Windows. That is just wrong! If you use the main method instead of the WinMain as an entry point in your programs, that is just fine. But that the CRT does the tokenization for you, doesn't mean that the program doesn't do the tokenization by itself. It does. This becomes even more clear, if one compares the native Windows API (i.e. CreateProcess) for launching programs to the unix equivalents like execv.