"schtanislau" wrote: It will zip all folders and sub directories, but will it be possible i.e. to access functions from /source/utilities/test.brs from /source/appMain.brs ? I think not.
Regarding slowing the compilation time - last post in this thread🙂
That same thread is telling you that B/S interpreter will "slurp" all BRS files under /source, regardless of the directory (sub)structure. Everything will be #included, everything will be flattened, there are no packages and namespaces, it's equivalent to concatenating everything to one file.
And may i share personal opinion: there is no point of breaking your source to subdirectories, there is no point of splitting it to separate files either - unless you are sharing codebase between different projects. No need to split to multiple files till your source is at least 2000 lines long. No need to organize in subdirectory structure till you have at least couple of dozen files. Writing in a high-level language, that means at least 20k lines - which is a massive, massive, massive undertaking not likely to be your case. I just published a puzzle game and it is under 2k lines total. All code in one file - lock, stock, and barrel. So, umm...
I have all my brs files in one folder, and I prefer to keep them under 1000 lines, far under usually. I like separate files divided into various sections/categories, so I can have them open in multiple tabs and "see" everything I'm doing without scrolling up and down much. But yeah, it all just gets lumped together in the end.