Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <199911011635.KAA24316@pluto.xraylith.wisc.edu>
To: "Daniel C. Sinclair" <uf657 AT victoria DOT tc DOT ca>
cc: Colin Peters <colinp AT ma DOT kcom DOT ne DOT jp>,
        GNU-win32 <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: mingw32 DLL getting main args? 
In-Reply-To: Your message of "Mon, 01 Nov 1999 04:16:38 PST."
             <Pine DOT GSO DOT 3 DOT 95 DOT iB1 DOT 0 DOT 991101040605 DOT 20874A-100000 AT vtn1> 
Date: Mon, 01 Nov 1999 10:35:12 -0600
From: Mumit Khan <khan AT thor DOT xraylith DOT wisc DOT edu>

"Daniel C. Sinclair" <uf657 AT victoria DOT tc DOT ca> writes:
> 
> Why support something that is non-standard? This is supposed to be a
> minimalist Win32 compiler. Just because VC++ has _argc and _argv doesn't
> mean everyone else has to. There are other ways to get the command line
> too. The most standard being just saving argc/argv in global variables
> yourself. There is also GetCommandLine(), CommandLineToArgv(), etc...

One goal of Mingw is source level compatibility with MS compilers, and I
for one see no reason to move away from that.

> Many Win32 functions do the same thing as the C runtime functions. I'm
> using some of those. I have heard that a program and DLL should not use a
> different C runtime DLL - bad things can happen. My DLL will be used by
> many people with different compilers, even different languages. So I don't
> want my DLL importing anything from a C runtime DLL. 

I agree on this issue. I've made the change, but need to test it first 
before I unleash it. I was hoping to have a new runtime snapshot this week, 
but looks like it'll have to wait till the weekend.

The runtime snapshots are in
  ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/mingw32/runtime/

The current changes in my tree include (not exhaustive list):
  
  - lots of header additions -- wide character api prototypes, incomplete
    but a start; tchar.h additions; fixes to various DLL imported variables;
    MSVCRT fixes; 
  
  - quite a few w32api changes. Anders Norlander already has some of these
    changes, but there are a quite a few that I'm still working on. One
    remaining issue is merging in the changes that have been made to Cygwin
    development snapshot version, and that's what I need to do now.

  - Thread-safe C++ exception handling. This allows the use of pthreads
    (POSIX Threads) package. This is still experimental, and subject to
    change. You'll need my next release of gcc to take advantage of it
    however.
  
  - change in DLL startup code to avoid linking in CRTDLL/MSVCRT. Untested
    as of yet.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com