So, I was going through the code yesterday, and not to be a jerk or anything, but you guys aren't much for documentation, are you?
Just saying. Sifting through the code was rather educational, but it's now going to be awhile before I get around to writing any patches. Hell, in lieu of writing any patches, I might just document the code once I figure out what it's all supposed to do.
Documentation...?
Moderators: MtnViewJohn, chris, mtnviewmark
-
- Posts: 21
- Joined: Wed Jul 06, 2005 4:53 pm
- MtnViewJohn
- Site Admin
- Posts: 882
- Joined: Fri May 06, 2005 2:26 pm
- Location: Mountain View, California
- Contact:
-
- Posts: 21
- Joined: Wed Jul 06, 2005 4:53 pm
- mtnviewmark
- Site Admin
- Posts: 81
- Joined: Wed May 04, 2005 12:46 pm
- Location: Mountain View, CA
- Contact:
Caught!
You know, this started out as a little hack... and just grew! I usually like to document my code by having test suites that demonstrate how each object should be used. Alas, we didn't get into that groove for this project.
Perhaps a written up "walk-through-the-code" would be appropriate. It isn't really that big.
You know, this started out as a little hack... and just grew! I usually like to document my code by having test suites that demonstrate how each object should be used. Alas, we didn't get into that groove for this project.
Perhaps a written up "walk-through-the-code" would be appropriate. It isn't really that big.
I'm the "m" in "mtree.cfdg"