Skip to content

Conversation

@7heo
Copy link

@7heo 7heo commented Dec 11, 2025

Reflect the fact that this is a "Lexer for various shells" as described in the top comment, and not just a Lexer for Bash.

Bash is not just shell, it is definitely a more advanced language, with array support, better loops, the function keyword, the select command, file slurping, more expansions, more conditionals, etc.

Assuming that any shell script would be a "Bash script" is error inducing at best, novices might try, not knowing better, to introduce so called bashisms in a POSIX shell script, and even seasoned developers might be mislead and assume the wrong thing.

Calling it a "Shell" script costs nothing, is correct, and will prevent any such issues.

Note: I left the references to "Bash" in function names and such, as the functionality is independent of those, but to be perfectly correct, those should also be corrected.

Reflect the fact that this is a "Lexer for various shells" as described in the top comment, and not just a Lexer for Bash.

Bash is not shell, it is definitely a more advanced language, with array support, better loops, the `function` keyword, the `select` command, file slurping, more expansions, more conditionals, etc.

Assuming that any shell script would be a "Bash script" is error inducing at best, novices might try, not knowing better, to introduce so called bashisms in a POSIX shell script, and even seasoned developers might be mislead and assume the wrong thing.

Calling it a "Shell" script costs nothing, is correct, and will prevent any such issues.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant