Hi,
I'm working away on CRTLL with good progress (about 50 functions so far). I
have some questions though:
Right now I test as follows:
Running in a no-windows configuration. Only file in c:\windows\system is
crtdll.dll, renamed to ms_crtdll.dll.
crtdll is set to builtin, elfdll, so (i.e. no native)
I have a test winelib program which calls LoadLibrary() on its argument,
then uses GetProcAddress() to call crtdll functions.
I run the program with crtdll, then ms_crtdll and compare the resut. Use
--debugmsg +crtdll to verify correct dll is called.
I am guessing that winelib may be more relaxed about arguments etc than an
lcc/bcc/VC++ compiled .exe.
Should I also compile my test program under windows and try running it with
both libraries?
-Locking -at some point I will need to add locking code for MT safety. Are
there any issues (performance?) I need to be aware of using the win32
locking functions in the dll?
-MS docs state that crtdll is not very threadsafe, however I cant see any
reason why wines shouldnt be. I don't think any apps depend on non
threadsafe behaviour since by definition it is unpredictable. So I think it
may be worthwhile to make it MT safe. This would mean a large part of the
code could be shared with msvcrt.dll (way in the future). Also, under unix I
would expect more processes to be running so potentially it is more
important to be safe. Does this make sense?
-Wines "process.h" will conflict with the crt "process.h". Is it desirable
to have crt headers in the wine include dir, or should they be in
include/crt? (note I wont be writing headers for some time).
Ill send a patch for the changes at the end of the week. This will include
any functions that dont make the code less MT safe. Then it'll be a while
before I update while I try to make sense of the file handling and MT code
:-)
Cheers,
Jon
This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it and notify the
sender. You must not, directly or indirectly, use, disclose, distribute,
print, or copy any part of this message if you are not the intended
recipient. CREDIT SUISSE GROUP and each of its subsidiaries each reserve
the right to monitor all e-mail communications through its networks. Any
views expressed in this message are those of the individual sender, except
where the message states otherwise and the sender is authorised to state
them to be the views of any such entity.
Unless otherwise stated, any pricing information given in this message is
indicative only, is subject to change and does not constitute an offer to
deal at any price quoted.
Any reference to the terms of executed transactions should be treated as
preliminary only and subject to our formal written confirmation.
