Re: about lposix

["David Burgess" <dburgess@...>]

Reminds me,

FILE* buffers for stdin,stderr,stdout require some fiddling to get
redirection to work reliably, not to mention the dreaded \r\n vs \n
issues.

Also add the wildly different directory/file security models and APIs (this
impacts mkdir() for example).

If I may quote an example of these annoyances:

*nix - getenv(), environ

win - getenv() and GetEnvironmentVariable(), GetEnvironmentStrings()

Looks simple. However the two windows APIs return different results, win
has a user and system environment which get merged and the posix variant
getenv() does not do what one would expect (it certainly does not produce
what you get from a commandline "set").

The point being that some (many?) of the windows posix and posix-like
APIs are dysfunctional. You need to match the functionality rather than
match the function name.

DB


Doug Currie wrote:
> Superficially things look quite rosy; then you hit a brick wall. Off
> the top of my head...