In a message dated 3/6/05 11:08:33 AM, [EMAIL PROTECTED] writes:
In my own experience reading AOLserver code, what I'd really wished
for was more comments explaining WHY something was being done, as
opposed to merely what or how. (I suspect I've rambled on about this
in the past...)
Andrew is right -- there isn't enough "why" commenting in the code. I often write (or rewrite) sections of the code assuming folks understand the flow of all the callbacks and threading junk or that there's some nonexistent architecture overview guide. We really do need that overview guide which will be a lot of work. In the meantime, we could go back and add some comments around areas of the code which are very particularly odd -- how about we compile a list of these sections? I'm thinking Tcl init and connection handling and garbage collection can be complicated and could use some explaination in the code.
-Jim
2">
- Re: [AOLSERVER] New Config API'... Tom Jackson
- Re: [AOLSERVER] New Config API'... Andrew Piskorski
- Re: [AOLSERVER] New Config API'... Dossy Shiobara
- Re: [AOLSERVER] New Config API'... Andrew Piskorski
- Re: [AOLSERVER] New Config API'... Andrew Piskorski
- Re: [AOLSERVER] New Config API'... Roberto Mello
- Re: [AOLSERVER] New Config API's wh... Tom Jackson
- Re: [AOLSERVER] New Config API'... Dossy Shiobara
- Re: [AOLSERVER] New Config API's which document defa... Tom Jackson
- Re: [AOLSERVER] New Config API's which document default v... Jim Davidson
- Re: [AOLSERVER] New Config API's which document default v... Jim Davidson
- Re: [AOLSERVER] New Config API's which document defa... Andrew Piskorski
- Re: [AOLSERVER] New Config API's which document ... Roberto Mello
- Re: [AOLSERVER] New Config API's which document default v... Jim Davidson