Code Layouts
Posted: Sat Jul 16, 2022 9:25 am
Hi alll,
New poster, but been playing around with hobby OS since early 2000s. As a professional software developer for my 9-5, we often have pretty strict policies about how to organize code by functionality and directory layouts,and I find that bleeding over into my own projects pretty extensively. I'm not complaining because after all, it was developed with the input of a lot of people over many years. I find myself writing my OS stuff organized by functionality in directory structure and even writing assembler in a "modular" fashion. It does make things easier, as you can usually isolate different pieces and get them bullet proof so you only have to worry about the parts that are still being actively developed. I dont have an overly deep directory structure, but most of my source files are only a few hundred lines long at best.
How do you all organize your source for your projects?
New poster, but been playing around with hobby OS since early 2000s. As a professional software developer for my 9-5, we often have pretty strict policies about how to organize code by functionality and directory layouts,and I find that bleeding over into my own projects pretty extensively. I'm not complaining because after all, it was developed with the input of a lot of people over many years. I find myself writing my OS stuff organized by functionality in directory structure and even writing assembler in a "modular" fashion. It does make things easier, as you can usually isolate different pieces and get them bullet proof so you only have to worry about the parts that are still being actively developed. I dont have an overly deep directory structure, but most of my source files are only a few hundred lines long at best.
How do you all organize your source for your projects?