Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 10 Sep 2004 14:19:40 -0500 (Central Daylight Time) From: "David A. Rogers" To: Chuck McDevitt Cc: cygwin@cygwin.com, Dave Korn Subject: RE: cygwin 1.5.11: execv doesn't set argv[0] on Windows programs In-Reply-To: Message-ID: X-Warning: UNAuthenticated Sender MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes On Fri, 10 Sep 2004, Chuck McDevitt wrote: > argv and argc are concepts from the C runtime, not the Windows OS. > > The actual entry point to your program is to a routine that calls the > initialization routines of the C library, then calls winMain. > Yes, certainly. The point I was making was that the information was available in a true win32 app. David Korn implied that the WinMain call was the only access to the calling arguments that were available to a win32 app. That is not true, as I showed. dar -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/