CompuServe Messages

#Desirable Source Length

    19-Feb-90 19:23:36
Fm: Steve Bennett/SYSOP 76702,1071
To: David Hamkins 76515,1650
Actually, if you take breaking code into modules to it's logical conclusion (ie, one function to a module…), then finding your functions becomes the easiest thing in the world. Just name each module after the function it performs. Same thing applies to closely tied functions. (Like, I might put the functions get_record(), find_record(), and set_record() in a single module called RECORD.C — It's pretty obvious where the functions are at…) However, as I mentioned in an earlier reply, if you're the only one who will ever have to deal with the code, do it whatever way suits. But only if you are certain nobody else will need to work with it.