What's your habit to document this?# Java - 爪哇娇娃
g*y
1 楼
In a program, there are three blocks, A, B, C.
A must run before C, because C will change some data A depends on.
In logic flow, A -> B -> C is natural.
When you write the program, you definitely write it as A->B->C.
Question is: what's your habit to document the precedence relationship between
A and C?
In a 200-line code, it will never be a problem. But when you work in a project
with 10~100 classes, each with 100 ~ 3000 lines of code. No good
documentation could cost heavily.
Example: when you
A must run before C, because C will change some data A depends on.
In logic flow, A -> B -> C is natural.
When you write the program, you definitely write it as A->B->C.
Question is: what's your habit to document the precedence relationship between
A and C?
In a 200-line code, it will never be a problem. But when you work in a project
with 10~100 classes, each with 100 ~ 3000 lines of code. No good
documentation could cost heavily.
Example: when you