saulius2 at ar.fi.lt
Mon Sep 11 03:43:50 CDT 2006
* On Sun, 10 Sep 2006, Aaron Slunt wrote:
> I was interested in starting to play with wine and maybe even build a
> few functions for it...but then I realized that it's low-level coding,
> something I'm not familiar with (higher level is more of my expertise).
> Correct me if I'm wrong, I could be looking at the wrong files :S.
You are welcome! :)
Can you refer to exact file names your were looking at?
> Does anyone have any good places to go to to learn about low-level
> coding, and afterwards coding for wine specifically?
For me Wine embraces libs for quite wide spectra of functions and not so
$ grep -rI "ioctl[^a-zA-Z0-9]*(" dlls/ | wc -l
$ grep -rIc "ioctl[^a-zA-Z0-9]*(" dlls/ | grep -v :0
As for me, low level coding is writing a device driver for linux kernel
:-] and using it from the Wine code.
But there is also a bunch of hardware platform specific issues also, like
advanced signal handling which may be needed for example to make remote
process operations work  or to implement ntoskrnl and make safedisc
All that stuff needs knowledge of glibc programming at least, I guess.
So maybe you should read recent libc.pdf if you are interested into this
Also, some guys are working on DCOM/OLE stuff  which seems to be quite
low level for me sometimes (wire-protocol compatibility).
Going further (upper?) most of Wine code tries to use WinAPI, which I
doubt should be considered as low-level. To get into basic Wine coding it
may be usefull to review Janitorial Projects  and maybe to hang on one
of it? :)
Without naming exact Wine component or functionality you are interested in
I doubt someone will answer you more specifically :-P
More information about the wine-devel