in reply to So much interconnectedness - good or bad?

It's not necessarily bad; it depends on the situation. The purpose of procedural modules is to promote code re-use and stop you from re-implementing the same thing in multiple places. If it's doing that and it's maintainable, it's fine.

On the other hand, if the modules that the various functions are in is haphazard, the modules are difficult to maintain, or if all programs end up including all four modules, it's worth spending some time coming up with a better design.

  • Comment on Re: So much interconnectedness - good or bad?

Replies are listed 'Best First'.
Re^2: So much interconnectedness - good or bad?
by kiat (Vicar) on Dec 17, 2004 at 05:27 UTC
    Ah, thanks sgifford!

    So the crucial thing here is whether the interconnectedness is structured (structured mess, sort of) and whether the entire code base is maintainable. Hm...will bear those in mind :)