The cases when it comes to parameter parsing on Linux and Unix operating systems are things like:
* A POSIX-conformant shell parsing a command line, in a shell script or entered interactively, into an argument vector.
* systemd parsing a string in ExecStart= in one of systemd's service definitions into an argument vector.
* Things that parse .desktop files, as given in the article.
* execlineb or nosh parsing a file into an argument vector.
- http://skarnet.org/software/execline/grammar.html
- http://jdebp.eu./Softwares/nosh/guide/nosh.html
* init parsing single fields of records in /etc/ttys or /etc/inittab into argument vectors.
* cron programs parsing fields in crontab records into argument vectors.
and so forth. These are all subtly or blatantly different, and the headlined article has glossed over this to a degree.
The cases when it comes to parameter parsing on Linux and Unix operating systems are things like:
* A POSIX-conformant shell parsing a command line, in a shell script or entered interactively, into an argument vector.
* systemd parsing a string in ExecStart= in one of systemd's service definitions into an argument vector.
* Things that parse .desktop files, as given in the article.
* execlineb or nosh parsing a file into an argument vector.
- http://skarnet.org/software/execline/grammar.html
- http://jdebp.eu./Softwares/nosh/guide/nosh.html
* init parsing single fields of records in /etc/ttys or /etc/inittab into argument vectors.
* cron programs parsing fields in crontab records into argument vectors.
and so forth. These are all subtly or blatantly different, and the headlined article has glossed over this to a degree.