Linked by Eugenia Loli on Mon 29th Oct 2001 17:25 UTC
Original OSNews Interviews WINE is definetely not an emulator. Neither a runtime. Wine is an implementation of the Windows 3.x and Win32 APIs on top of X and Unix featuring a Windows compatibility layer. Wine provides both a development toolkit (Winelib) for porting Windows sources to Unix and a program loader, allowing unmodified Windows 3.1/95/NT binaries to run under Intel Unixes (some screenshots here). Wine does not require Microsoft Windows, as it is a completely alternative implementation consisting of 100% open source Microsoft-free code, but it can optionally use native system DLLs if they are available. WINE's project leader and CodeWeavers' software engineer (a company which sells a modified WINE version), Alexandre Julliard, answers a series of questions to OSNews regarding the project and its future.
Permalink for comment
To read all comments associated with this story, please click here.
mmap() on Beos?
by Anon. on Tue 30th Oct 2001 21:18 UTC

Zenja said: mmap() isn't the vain of BeOS programmers - BArea's will do just fine. The only problem is that the port is no longer trivial and cannot be done with minimum code changes (like my half arsed attempts with Qt and Konqueror, done in less than a day). Since the porter isn't the person who initially designed the app, the time needed to reimplement the functionality is much higher than what your averaged bored geek is willing to spend. Hence its easier to cry "we want mmap() and select() and AF_UNIX IPC" than to sit down and work around the problem. Having the kernel and applications live in seperate address spaces is a different story, though. I say: I'm no pro programmer, but is it possible to create an mmap() function on BeOS that uses BArea or something like that. Just create a library to translate the mmap() calls of Wine and other programs....