home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.win32
- Path: sparky!uunet!psinntp!nstn.ns.ca!cs.dal.ca!iisat!mkseast!dale
- From: dale@mkseast.uucp (Dale Gass)
- Subject: Re: POSIX interface/Access to WIN32 calls
- Organization: Mortice Kern Systems, Atlantic Canada Branch
- Date: Mon, 25 Jan 1993 19:02:04 GMT
- Message-ID: <1993Jan25.190204.3950@mkseast.uucp>
- References: <1993Jan18.205847.13264@sobeco.com> <1993Jan21.070314.15778@ryn.mro4.dec.com> <lltljvINN48a@exodus.Eng.Sun.COM>
- Lines: 30
-
- db@argon.Eng.Sun.COM (David Brownell) writes:
- >> > Can I in some way make WIN32 calls from
- >> >a POSIX compiled application.
- >>
- >> No, you can't mix subsystems.
- >I've heard this before ("can I both POSIX and WIN32 APIs" seems to
- >be a FAQ), but never a rationale. What's the point of preventing use
- >of standard (POSIX) APIs and others (WIN32, ...) in one program?
- >
- >I'm not after a "because that's the way it's built" answer, but rather
- >one that explains why that's a supposed to be good thing.
-
- I agree...
-
- I can see why the "compatability" subsystems like OS/2 don't have WIN32
- access; you want them primarily to run binaries built on and for other
- systems.
-
- But for the POSIX subsystem, you're not running binaries from other systems;
- you're running binaries which have to be specifically built to run on
- Windows NT. You're not creating a binary compatability box, but inventing
- a new binary format and a new penalty box which is incompatible with the
- native NT API's. To limit access to the WIN32 calls is insane...
-
- I think the whole point was missed here...
-
- -dale
- --
- Dale Gass, Mortice Kern Systems, Atlantic Canada Branch
- Business: dale@east.mks.com, Pleasure: dale@mkseast.uucp
-