source code may be getting a bit intimidating

Lubomir I. Ivanov neolit123 at gmail.com
Sun Jan 6 07:19:01 PST 2013


things are always getting messy when large files have to be maintained
and edited in a code base, down the road.
rules of thumb on my end for implementation files is "keep them under
1k LOC" and its better to have more files that a couple of bigger
ones.

even if no major issues pop out, in C, at least function names would
start making less sense as more are added.
"add_button_to_something()", will have to be prefixed to
"something_add_button_to_something()".

but inevitably more and more features will be added to subsurface
which will increase the code base and will affect files like gtk-gui.c
and divelist.c (which are two of the bigger ones).

what do you think can be done to improve the code base? how can we
start organizing the code base into a better structure?
i'm quite interested in the opinion of people who wan't to contribute
but are getting lost and potentially give up (if there are such of
course).
is this nonsense talk at this point...?

lubomir
--


More information about the subsurface mailing list