On Tue, Jul 14, 2015 at 11:13 AM, Charles Daffern <seejay...@gmail.com> wrote:
> On 14/07/15 06:49, Dmitry Bogatov wrote: > > Guile is for situations, when script is mainly calls other programs, > > but still needs moderately complex logic of text manipulation, > > compraison and mapping. Recently I wrote script, that had to emulate > > map(data structure). Well, I would prefer that is was part of Bash. > Bash has associative arrays, which is the data structure other languages > refer to as a map. > > Second (possible) reason is that it allows Bash to be extended by every > > user in Emacs way. After all, Guile was created for this to be possible. > Bash has coproc, which allows 2-way communication with other processes > including scripting language interpreters. (Whether that's a good idea > or not is a different story, but it's possible.) > Bash is a language so sure it can do some kind of things...just not as many things as guile. I think adoption would be difficult considering even a useful loadable builtin like "finfo" has not found its way into default installations, but for instance I can imagine bash programmable completion could go another level with an embedded interpreter that lets you access the readline internals. Other examples could be things like gnu parallel, sqlite3, or parsing xml or json...of course there are external tools for this and you can compile a loadable builtin, but being able to tinker with a small script and having your query result directly into a bash array without further parsing is nice too.
