<Amaranth> mark is talking
<fishsticks> where
<Amaranth> googleplex
<Amaranth> we're doing introductions
<rikai> gah!
<rikai> How should developers aim stuff aim for POSIX compliance(what dash(the edgy bash(?) replacment) wants) when the IEEE charges very high rates for POSIX documentation and does not allow on-line publication of the standards?
<rikai> Thats something i'd like to know x.x
<Amaranth> rikai: linux man pages tell you if something is POSIX or not
<rikai> Amaranth, eh?
<rikai> Amaranth, i'm talking about making something that apparently isnt POSIX compliant, POSIX complaint.
<rikai> Not finding out weather something isn't POSIX complaint or not
<Amaranth> rikai: you test it
<Amaranth> POSIX is nothing as long as it works on linux, solaris, bsd, etc
<rikai> Amaranth, with? i see no POSIX compliance test suites...
<Amaranth> you install all those and test
<rikai> how do you debug posix complaince if you've got no reference though? how do you tell why something isn't POSIX compliant if there's no reference for what is and what isn't?
<rikai> example: 299: Syntax error: Bad substitution
<rikai> line 299 being: FOUND_DEP in ${FOUND_DEPS[@]}; do
<rikai> how is that not POSIX compliant?
<rikai> It just doesn't make any sense to me debugging POSIX standards compliance without having a frame of reference as to what those standards ARE.