I have been testing Wine and Winelib using the examples
contained in the book "Programming Windows 95" by Charles Petzold (a
classic).
I think this can be a nice way of testing Wine:
- the source is available... to whoever owns the book or can get it at
a library
- the programs are simple and very well documented
- they do exihibit problems in Wine (at execution time) and in Winelib
(mostly at compile time)
- they cover relatively diverse subjects (graphics, keyboard, message
handling, try the API cross-reference...)
The detailed results of these tests are available at:
http://www.multimania.com/fgouget/wine/PrgWin95/
Some statistics:
- there's 102 C files, 4 C++ ones, 66 C files compiled fine, none of
the C++ files compiled correctly
- the first 5 chapters contain 20 examples, 8 show some anomaly and 6
exhibit a behavior which I'm not sure is correct
I used a perl script to help in generating/updating the web
pages, generating Makefiles for Winelib, cross-referencing the API calls
(hence my recent interest in dumpbin/pedump), generating a tar file
ready for download, etc. I packaged this script so that it can be
adapted to other books. You can get it from:
tp://localhost/fgouget/wine/booktesting-en.shtml
This page also explains the procedure in a little bit more
detail.
Now what?
- I have not fully tested all the examples in the book. I'm currently
at chapter 11. Nine more to go.
- I have not yet updated the Makefiles since the Winelib compilation
procedure changed. I shall update this.
- I have two other books to test:
- Programming MFC which I will test with Wine only (unless someone
can tell me how to compile the MFC with Winelib)
- The developper's guide to the Win32 API for Windows NT and Windows 95
- There's various enhancements to do to the perl script I use
and the most important:
- Fixing the problems uncovered by these tests
Well, that last one is the hard part. For most of them I really
don't know how to do that. For instance one problem is that in managed
mode the resize events seem to be lagging behind the actual window
resize. I'm really not familiar with the message sequences in Windows so
this seems way out of my league. That's why I'm kind of looking for
people interested in tackling them. Of course I would provide all the
support I can. If you don't have the book, I do. So I can tell you what
the code is doing, what it expects, tell you exactly what happens when
running in Windows, ...
Maybe I could try to feed the results of these tests to the bug
tracking system, let me know if this would be a good idea. I'm open to
other suggestions.
--
Francois Gouget [EMAIL PROTECTED] http://www.multimania.com/fgouget
In theory, theory and practice are the same, but in practice they're different.
