In article ,   
   Krishna Myneni   wrote:   
   >On 3/23/24 04:30, mhx wrote:   
   >> My current project has 13,938 lines of code (and documentation).   
   >> That is too large to keep every detail of it in my head.   
   >>   
   >> The reason to not factor it in a number of smaller files is that   
   >> there are many (unavoidable) global variables and data blobs. These   
   >> global variables prevent me from dividing the application   
   >> up into smaller programs that can run standalone. They also prevent me   
   >> from documenting sub-tools, and giving such tools their own help words ...   
   >   
   >Without seeing the code, I probably can't say much about how to separate   
   >it into multiple files, each a logical unit.   
   >   
   >Global data by itself shouldn't prevent you from separating the code   
   >into multiple files. The files have external data dependency which can   
   >be documented at the top of the code.   
   >   
   >I've used the modular programming[1] approach successfully to write and   
   >maintain Forth applications which are composed of thousands of lines of   
   >Forth source, but each module is logically separate, and, in a few   
   >instances, relies on externally declared global data.   
      
   I guess that separates the men from the boys.   
      
   >   
   >--   
   >Krishna   
   >   
   >Ref.   
   >1. https://github.com/mynenik/kForth-Win32/blob/master/doc/modular-forth.pdf   
   >   
   >   
   >   
   >   
   >   
   --   
   Don't praise the day before the evening. One swallow doesn't make spring.   
   You must not say "hey" before you have crossed the bridge. Don't sell the   
   hide of the bear until you shot it. Better one bird in the hand than ten in   
   the air. First gain is a cat purring.            - the Wise from Antrim -   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)