Daniel Becroft
2004-06-03 06:02:28 UTC
Hey all,
I am currently in the process of creating a small data structures
package, and doing the API documentation as a I go.
My question is, as programmers, what information would you guys
like/need from the documentation regarding such a package? I know the
obvious stuff: class names, method names/signatures, etc, but would
something like efficiency information (big-Oh notation) be useful?
Thanks,
I am currently in the process of creating a small data structures
package, and doing the API documentation as a I go.
My question is, as programmers, what information would you guys
like/need from the documentation regarding such a package? I know the
obvious stuff: class names, method names/signatures, etc, but would
something like efficiency information (big-Oh notation) be useful?
Thanks,
--
Daniel Becroft
; =================================
"Real computer scientists don't comment their code. The identifiers are
so long they can't afford the disk space."
"Blue sparks and white smoke, the two most expensive components of any
electrical system, and once used up will cost a fortune to replace."
Daniel Becroft
; =================================
"Real computer scientists don't comment their code. The identifiers are
so long they can't afford the disk space."
"Blue sparks and white smoke, the two most expensive components of any
electrical system, and once used up will cost a fortune to replace."