Issues in README.md

[jashelio]

After the table, the text is "Having your students/developers perform native installations on their individual machines can lead to unexpected challenges do to the variety of different environments this creates. " That should be "due to".

In the Python section, we have the reader check their version of Python by running the command
python3 --version
Doesn't Windows install the interpreter for Python 3.x with the old name "python"? If so I don't think that the installation of WSL would change that, but I don't know it from personal experience. Perhaps it uses python3.exe as an alias now.

According to the scripts, it looks like the default grammar file is named "spec", and the second choice is "grammar". The former is not documented anywhere. Also, It looks like the plain plcc script does not assume any default grammar file name.

[StoneyJackson]

@jashelio

After the table, the text is "Having your students/developers perform native installations on their individual machines can lead to unexpected challenges do to the variety of different environments this creates. " That should be "due to".

Good catch.

In the Python section, we have the reader check their version of Python by running the command
python3 --version
Doesn't Windows install the interpreter for Python 3.x with the old name "python"? If so I don't think that the installation of WSL would change that, but I don't know it from personal experience. Perhaps it uses python3.exe as an alias now.

WSL 2 installs linux in a virtual machine. I don't know for sure, but that sounds like it would have a separate path, and any Python installed would be a Linux-style install. This seems to confirm: https://stackoverflow.com/questions/78033592/do-wsl-use-the-python-installation-which-is-installed-on-windows-host#:~:text=You%20can%20install%20Python%20within,command%20sudo%20apt%20install%20python3%20.

According to the scripts, it looks like the default grammar file is named "spec", and the second choice is "grammar". The former is not documented anywhere. Also, It looks like the plain plcc script does not assume any default grammar file name.

For several reasons, I prefer the behavior of the Python plcc script which doesn't have a default file and would prefer to remove the "default code" in the plcc bash script.

1. It would simplify documentation.
2. It would simplify the script.
3. Personally, I always type the name of the file, and I teach my students too as well.
4. Then we don't have to agree on what the default file should be (IMHO, these files should be called a "specification" and not a "grammar" since it includes semantics, and it should have an extension of .plcc to make it clear that its syntax is defined for use with plcc.)

[StoneyJackson]

Typo fixed.

[jashelio]

@StoneyJackson :

For several reasons, I prefer the behavior of the Python plcc script which doesn't have a default file and would prefer to remove the "default code" in the plcc bash script.

I am in favor of this, for the same reasons that Stoney stated.