Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Fri, 10 Sep 2004 14:19:40 -0500 (Central Daylight Time)
From:	"David A. Rogers" <darogers AT speakeasy DOT net>
To:	Chuck McDevitt <cmcdevitt AT ABINITIO DOT COM>
Cc:	cygwin AT cygwin DOT com, Dave Korn <dk AT artimi DOT com>
Subject:	RE: cygwin 1.5.11: execv doesn't set argv[0] on Windows programs
In-Reply-To:	<OF11317D53.7B086299-ON85256F0B.006544CE-85256F0B.0065AD2C@abinitio.com>
Message-ID:	<Pine.WNT.4.44.0409101356140.2300-100000@drogers2k.spss.com>
X-Warning:	UNAuthenticated Sender
MIME-Version:	1.0
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/

- Raw text -