> At 03:08 PM 1/15/01 +0100, Patrik Stridvall wrote:
> > > On Sun, 14 Jan 2001 [EMAIL PROTECTED] wrote:
> > > > Let me know if anyone is interested.
> >
> >However there is several problems to overcome before that.
> >The most import ones except for the problems above is
> >
> >1. BeOS doesn't have mmap
> >2. BeOS doesn't have recvmsg/sendmsg
> >3. BeOs doesn't provide any way to manipulate LDT:s
> > (not needed for Winelib eventhough I think it requires
> > that some part of Wine is fixed to cope with this.
> > I other word more strict separation of Win16 and Win32)
> >
> >There are some more minor problems that are listed on
> >the website somewhere.
>
> Last voice from the list was that we're waiting on BONE, for some features
> relating to sockets. To be honest, I've about given up on Be since it's
> taken so long to get BONE out, and I'm completely out of the loop now.
I'll
> happily keep the web site up for whoever wants to use it, though. Make
sure
> you start with the latest patch we have..
>
> If you ask Patrik really nicely, and if he's not mad about having done all
> that work for an apparently failed project, you might be able to get him
to
> merge the last bewine patches to the current source..
>
> Anyways, good luck if you try to revive the project. Main thing we were
> missing were developers that knew BeOS to get past the above obsticles.
>
> --Doug
<RANT>I had an idea contemplating the PPC port and I have some preliminary
patches for 20001222 that might affect wine in general. I was considering
one day that a sort of pre-interpretation system could be implemented, where
the entire application is analyzed quickly and then modified as it is loaded
into memory to suit the particular architecture's needs. I've not seen much
in this way discussed on this mailing list, and I have also not received
much input, be it positive or negative, as far as this idea is concerned. I
honestly believe that some system hurdles such as the LDT problem might be
overcome on the behalf of wine as an interpreter if this given some thought.
On the subject of mmap, I remember that one of my friends was working on a
"portable mmap" idea but never completed any code for it - an idea that
might be an excellent thought as well for wine. As I have seen it, the
developers of wine have put an immense amount of effort into understanding
MFC and the various quirks of such a horrible but extensively (almost
universally :-( ) used operating system set as windows is, but I am suprised
that the modularization to bring wine to other systems is not as big of a
focus as I thought it would be upon first taking interest in wine. Wine has
come a long way, but it still needs a bit of polishing before it can become
a truly excellent app. </RANT>
------
Michael
