On Wednesday, 7 October 2015 19:11:35 UTC+2, Jeroen Demeyer wrote: > > On 2015-10-07 18:50, Bill Hart wrote: > > > > > > On Wednesday, 7 October 2015 18:33:01 UTC+2, Jeroen Demeyer wrote: > > > > On 2015-10-07 18:23, Bill Hart wrote: > > > Cygwin also provides a POSIX environment, so I'm not sure I > > understand > > > why this is an "elephant in the room". > > > > It's an elephant in the room because your original post completely > > seems > > to ignore any possible problems with the POSIX layer, while the > POSIX > > layer is where most of the problems on Cygwin come from. > > > > > > You mean there were bugs in the way posix was implemented in Cygwin? > Well, it's not really bugs. The problem is that some things just don't > have a Windows equivalent. fork() is a good example, that just doesn't > exist on Windows. >
Sure, but this doesn't make porting to Windows impossible. MSYS2 of course emulates fork/exec just like Cygwin. And yes, you still have the BLODA (big list of dodgy apps) that can cause fork to fail. Whilst there are some Windows shells that try to deal with this issue, they aren't gaining much mindshare. In many cases, one can find an alternative to fork/exec (which apparently isn't even the most efficient way to do things on Linux much of the time that it is used). In the end, a truly native Windows app wouldn't use fork. But I'm not advocating going the whole hog right away. There needs to be some intermediate steps between no Windows support and complete native Windows support. MSYS2 is a practical approach which serious Windows developers will take seriously (unlike Cygwin). Bill. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
