[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1363581023.15703.25@driftwood>
Date: Sun, 17 Mar 2013 23:30:23 -0500
From: Rob Landley <rob@...dley.net>
To: musl@...ts.openwall.com
Cc: musl@...ts.openwall.com
Subject: Re: question: hard-coded file descriptors in
stdin/stdout/stderr
On 03/17/2013 11:08:24 PM, Rich Felker wrote:
> On Sun, Mar 17, 2013 at 10:50:01PM -0500, Strake wrote:
> > On 17/03/2013, Rich Felker <dalias@...ifal.cx> wrote:
> > > Rather,
> > > it makes OUR lives easier, because FOSS projects can just target
> POSIX
> > > and keep their cores simple
> >
> > Actually, we can do that anyhow.
>
> Well of course those of us who don't care about Windows support can do
> that. The problem is that many people do care about Windows support,
> and thus we're stuck with lots of mess. I'd really like to see a next
> generation of applications that aren't full of hacks for
> "portability".
If Windows gets left behind on the PC the way Dec's Unicos got left
behind on the minicomputer, and in the new world of smartphones nobody
does Windows, problem solved. (And speaking of portability hacks, 64
bit Windows is LLP64, not LP64. On 64 bit windows, "long" is 32 bits.)
I understand what Cygwin tried to do, and why it's a mess. (Timesys
supported its own fork of that when I worked there.) I understand what
mingw tried to do, and why it's a different mess. (I used that to test
tinycc's windows mode under wine.) I don't understand why this new
approach thinks it won't encounter the problems of either previous
project. I'd wait to see code, except I haven't got a windows test
environment and don't want one.
Rob
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
