Re: [PATCH v2 5/8] builtins/source: parse the -i option

[konsolebox]

On Mon, May 20, 2024 at 4:43 AM Robert Elz <kre@munnari.oz.au> wrote:
>   | A builtin is far more convenient, isn't it?
>   | Much more ergonomic.
>
> Only when it is really needed.

If there's a standard way of writing multi-script applications (and
reusing libraries) in bash, people will ask less about it in SO or
#bash and just have to read the manual.  If they still have to ask, at
least the answers will become much simpler and more straightforward.

Hi-voted questions like this with workaroundish
external-binary-dependent answers wouldn't exist:
https://stackoverflow.com/questions/59895/how-do-i-get-the-directory-where-a-bash-script-is-located-from-within-the-script

That's the highest voted bash-related question in SO by the way.

Not to mention people who like to write multi-script applications like
the way they do in C, Ruby or other languages will be happy if they
are able to do it in Bash too.

I wrote my include solution years ago and people still write their own
solutions from scratch.  So much time wasted for an obvious feature
almost every language has.

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.


--
konsolebox