Yes, it's true ... some of the "modules" reference each other's symbols.
There are a couple of situations where I got a bit messy. Sorry :(
serv_crypto.c really isn't a "module" in the sense we've been discussing.
r5326 | ajc | 2007-07-24 14:48:12 -0400 (Tue, 24 Jul 2007) | 1 line
Changed paths:
M /trunk/citadel/user_ops.c
'master user' hack is now an #ifdef instead of commented out
--
If you're attempting to port Citadel to Windows, however, you're touched.
There's a bit of a difference.
If you're inside a module you're already privileged.
I'd just noticed that client prior to reading your post but I haven't looked at it yet.I'm working on cleaning the module inteface with my ideas for auto init functions to forward my module.
It's a good start. I wonder if the existing stress test client (stress.c)
could be used as the basis for the test suite.
Ah, so this is for the test system, use artv to import a load of test data let the server process it, export the test data and compare it with what we think it should be.Isn't it great that these features to assist testing are already built in.I'm thinking we need to start describing some tests t
