At 20:28 19.09.99 -0400, you wrote: > BTW, and I meant to ask earlier, how hard/easy was to read the >code/docs/etc? (Comment & clarity-wise.) If we want to add more >developers, these things need to be taken care of, and I don't have >enought to perspective to say... yo, well I guess I can't help you much here, cause I think the source code is very well organized & well commented; I had no trouble reading the code, (although I didnt understand some things, done in the code; but thats only due to my little knowledge of JVM internals); the docs are well enough; one thought though: you could provide "hooks" for [future] coders; by hooks I mean something like a little ToDo inside the code, at the place where it should be done, this could be something like little job descriptions for people that look at the code but don't know where to start; eg: some code (function,...) that could be implemented more better, (although thats somehow done already, it could be more direct, so that people like me could start fooling around with the code); another thing: is there something like javadoc for C[++]? this could help up understanding the code, also the purpose of the code could be added to this doc; murphee *************************************** UNITE FOR JAVA -> www.javalobby.org Check this out -> www.jos.org My site -> www.angelfire.com/co/werners *************************************** ... and the fact, that i haven't put a gun to my mouth yet, proves that i'm a winner! Al Bundy _______________________________________________ Kernel maillist - [EMAIL PROTECTED] http://jos.org/mailman/listinfo/kernel
