3 ms·
How is || exit 1 harder to understand? With the exception of GNU autotools, I know of no backends which would emit shell programs. People write programs in she
by Annatar 7y ago
How is || exit 1 harder to understand?
With the exception of GNU autotools, I know of no backends which would emit shell programs. People write programs in shells.
- sitkack 7y agoI used that as an example of when using the portable idiom makes the most sense and not something specific wrt bash. But in this case I know of https://github.com/BYVoid/Batsh https://github.com/BYVoid/Batsh and https://github.com/kanaka/mal/tree/master/bash https://github.com/kanaka/mal/tree/master/bash
- mlyle 7y ago???? Autotools is written in M4.. M3/M4 were developed by K&R to help automate generating mostly shell programs. In 1974-1977. For someone who purports to be so oldschool, you're sure missing a lot.
- Annatar 7y agoPlease take a moment to pause and consider what you're writing. Someone here wrote "let the backend generate correct code". I responded that people usually write shell programs, not backends.
- mlyle 7y agoYou wrote that you know of no backends--- but we have a long history of macro preprocessing/expansion of shell scripts. M4 would excel at this adaptation... Which isn't even necessary, because everything posix conformant has "set -e". And if "posix" isn't good enough, the Bourne Shell back to 1978 has it (probably earlier). You are hilarious, bro. :D
- Annatar 7y agoM4 is a generic preprocessor, not a backend shell program compiler. And I'm not your bro.