POSIX Standard and Compliance

[andrewwoods]

Description

What is required for POSIX compliance? Do i need to care?

According to It's Foss

When code is compliant, it’s easier to move to another system; very little code rewrite, if any, would be necessary. When code can work on different systems, the use of it expands. People using other systems can benefit from the use of the program. For the budding programmer, learning how to write programs that are POSIX compliant can only help their career.

Since POSIX is about portability and interoperability, I probably should — especially if I want Opal to go beyond "it works on my machine". Research is required to figure out what POSIX means for the project.

Expected Outcome

I need a list of criteria that I can apply to bash scripting, and data formats. I'm only planning to support Bash. So I'm only really interested in cross OS interop, as it applies to Bash. In the future, I may consider support ZSH, but I've never used it in earnest. So ZSH is not on the roadmap.

Describe alternatives you've considered

"It works on my machine". But I want to use Opal on Linux servers, so I need to think about cross OS interop more in the design phase.