diff options
author | Mohammadreza Khellat <mkhellat@gmail.com> | 2020-12-01 13:54:34 +0330 |
---|---|---|
committer | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-12-02 01:44:56 +0000 |
commit | dc3f7229cdecede42fc4b6f806a89921ef5d13f2 (patch) | |
tree | 265197b2765153d13f983bf50c2f0d66a72694c4 /reproduce/software/bibtex/mpi4py.tex | |
parent | a9786200d5ed5bde30cb29b445e2a6af06694b2e (diff) |
Minor modification of Completeness criterion conditions
Before this commit, condition (1) for the Completeness criterion was
referring to POSIX compliance. POSIX is a very detailed dynamic standard
which goes under revision continuously and not a lot of operating systems,
GNU/Linux included are completely/officially POSIX-compliant. Furthermore,
not all sections of the huge 4000 pages standard are really important
specifically to the current Maneage functionality.
With this commit, condition (1) has been replaced by a looser condition of
execution within a Unix-like OS. Also since the term environment might have
been mistaken with the term "Operating Environment", it was replaced by the
unmistakable term "environment variables" in conditions (3) and (5). Last
but not least, condition (2) was made more restrict by adding ASCII
encoding as the condition for storing the plain text files.
TO-DO:
POSIX could contain valuable ideas regarding portability of programming
practices. These can be taken advantage of later in providing necessary and
sufficient conditions for project completeness. Another idea could be to
make LFS construct or something else as a sharp definition for what we mean
by minimal Unix-like OS.
Diffstat (limited to 'reproduce/software/bibtex/mpi4py.tex')
0 files changed, 0 insertions, 0 deletions