I just took a quick look at some of the source to guage how hard it would be to get up to speed on the code. I was wondering if there was some documentation somewhere (I doubt there is, but who knows). In the pieces I looked at (macroquest.h/cpp eqlib.h/cpp) it appears to be just C code (i.e. not really using any of the features of c++ e.g. classes, templates, streams, references, etc.) Also, it seems to be pretty low level stuff. I would like to contribute something in the way of code but I dont think I have the time learn the code from scratch, and I have never done that much low level programming (except some assembly in college). Also, it has been probably 8 years since I've programmed in straight C, when I found c++ I never looked back, then about 3 years ago I switched to JAVA for most of my work, and now that they have perl like regular expressions in JAVA I have pretty much abandoned perl too.
I guess what my question boils down to: Is there anything I can contribute if I am not a low level programmer? Most of my experience is in OOD and algorithm development/analysis. I can't put in a ton of hours since I have a regular job, a newborn daughter, work on side projects, and an EQ habit to support, but I'm already reading the forums a couple times a day and can kick in some development time if there is anything to be done that my skills lend themselves too. (hell, I suppose I could even be a google bot for the main developers if they need to research something).
Eric
Documentation
Moderator: MacroQuest Developers
There is no source code documentation for this project that I am aware of. Also, the code does make use of classes when it comes to the Detours library, which is C++. Apart from that (and possibly a few other C++-only things such as allocation new variables inline within various scopes instead of at the beginning of a function, etc.) I believe it is all straight C.
I am not much of a low-level programmer either (although I fully understand all the concepts). Therefore I've tried to be of as much help as I can by working on new features and by excessively testing new iterations of the codebase against patches, etc. I try to help also by replying to messages here when possible, to help new users out or to offer an opinion about something.
But the "real" developers shall have to speak to your post, not just lowly me. Just had to put in my thoughts, though.
I am not much of a low-level programmer either (although I fully understand all the concepts). Therefore I've tried to be of as much help as I can by working on new features and by excessively testing new iterations of the codebase against patches, etc. I try to help also by replying to messages here when possible, to help new users out or to offer an opinion about something.
But the "real" developers shall have to speak to your post, not just lowly me. Just had to put in my thoughts, though.
Clawed
