On Tue, May 21, 2024 at 4:10 AM Chet Ramey <chet.ra...@case.edu> wrote: > > On 5/20/24 3:39 AM, konsolebox wrote: > > > It's rare for a topic about adding an import/include function to get > > so much attention like this I think it's time Bash takes the > > opportunity to implement it and hopefully properly. > > `Properly' is clearly in the eye of the beholder.
I'm sorry if I have to sound assertive on this one but I thoroughly thought about these things years ago and made a framework that works on a multitude of shells, allows both simple and pattern-based targets, and can be compiled (merged into a single file) with simple usage. Not to mention I actually wrote a multi-script application I know what people who write one want. I found the simplest formula that isn't limiting and is sound as proven by other shells besides bash that also work with it. The framework's design was heavily forged. Of course we're only talking about improving Bash here but that just means I have a solid reference and I know where to simplify things and where to adapt. This is why I was able to make the prototype script quickly the moment I decided to write it instead of a C implementation. Deciding what helper function to use was just a struggle. Error handling also makes the code verbose it's better presented in a script first before it's approved. So what I'm saying is it's not just in everyone's own perception. It's also in the experience. -- konsolebox
