[Q] Can bash compatibility in toysh be turned off during build time and during run time?

[xplshn]

Also, does it respect POSIXLY_CORRECT=1? (even tho POSIXLY_CORRECT=1 doesn't really make Bash "POSIXLY CORRECT")

It'd be great if one could make Toybox NOT rely on any non-POSIX behavior, is that part of the roadmap?

[landley]

Not yet. I might add that later (since it is a feature bash has), but I'm not likely to put a LOT of work into reimplementing dash. You can install dash alongside if you really need a hairshirt to make sure your code doesn't step out of line.

[xplshn]

No no, I didn't mean to imply something like dash was needed, dash itself doesn't respect standards either, it has deleted lots of functionality needed for an interactive shell, I was simply asking if non-POSIX features were implemented in a way that allowed to know that they are being used and also to disable them, and now that I know it isn't that way, it'd be great if they were implemented in a separate, optional file. So that the burden of developing an entire shell could be broken down into two milestones:

1. POSIX Shell compatibility that passes the shellcheck tests
2. BASH extensions that some users may need. (which Busybox's ash does have)

Anyways, thanks for everything, toybox is a great resource when it comes to implementing these tools on my own, the source code is small and mostly readable for someone that doesn't code a lot in C.