Hello, I liked your article. I have a project that is more than 5000 lines long, not counting the import modules, I also like you to test the include, but we lose information, so when hot, no problem but it is not viable, I have a very large screen but the cut in half is not enough, more often the editors have small beug, between the VS-Code mastodons which end up pedaling and the very light ones whose references are absent like Geany, I'm all alone so I'm doing well but if another person like in a company had to be on the same project ... I remember we had 3 big screens .... in short, that doesn't solve the very big ones projects we can also force to work and remodel in import moreover a question torments me we are not talking about exporting does import also export ??? So the / proc functions but as the "import" are objects then the data redefinitions ... well I discuss like that I think aloud. But I understood correctly and this applies to all Projects requiring code lines. On the AS400 we could do everything modular but everything communicated and there was one like shm.h and ipc.h of UDS and SDS and DS data-structures with pointer which made it possible to make the programming relational even the file declarations could be shared in "open data space". Well, I'm not asking for time, for example we had halved the purchase request and purchase validation program with independent files. There is also a lack of documentation (example related to definitions) for example as soon as you go down in the system see IPC SHM when you want an application to communicate with external programs to name a few ... In short in all this I find that NIM by itself is Reliable, certainly that they would need more people but that is another story. Maybe remember that Open-source does not want without donation;)
I use google for the translation excuse me
