This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: unix user - who BOYCOTTED microsoft a long time ago - still not paid for microsoft legal infringements


On 01.05.2015 16:46, John D. Hendrickson wrote:
> i've been findign allot of microsoft hacks in Unix code

I had to re-read your message a few times to make any sense of it. I'll try to
sum it up as best as i can, please verify that no meaning was lost in the process.

Your issue is with portable projects (that can be compiled for W32; you seem to
focus on Cygwin specifically, but i presume you mean any W32, not just Cygwin -
i.e MinGW too). They are:

1) Getting ifdefs for W32/Cygwin-specific code. You dislike that this damages
readability, but since no W32/Cygwin-specific code gets compiled for
non-W32/Cygwin platforms, you're kind of "ok" with this.

2) Getting redesigned to fit W32/Cygwin better (you gave no specific examples,
but i presume that you've meant this too; if you didn't, please say so) - like
getting functions that are no-ops everywhere except on W32/Cygwin, getting
abstractions that are only meaningful on W32/Cygwin.

3) Getting features that only have meaning on W32/Cygwin (or have meaning on
other platforms as well, but you dislike these features), but which introduce
dependencies that otherwise would not be there.

Does that cover it?

-- 
O< ascii ribbon - stop html email! - www.asciiribbon.org

Attachment: 0x922360B0.asc
Description: application/pgp-keys

Attachment: signature.asc
Description: OpenPGP digital signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]