We can place it to the normal download page (manuals and guides linked above), I just wonder why it now lists:
GnuCOBOL 2.2 and then directly skips to GnuCOBOL 3.2 as GnuCOBOL 3.1 is expected to get its release (and the grammar between 3.1 and 3.2-early-dev is still identical [or can be easily made] isn't it?).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just wonder why it now lists GnuCOBOL 2.2 and then directly skips to GnuCOBOL 3.2
I updated the changelog by reading the commit logs for trunk and I got confused when [r3263] turned the Pangea branch into trunk. It looked like 3.1 had been skipped entirely and after [r3263] I skipped all the 3.1 commits that weren't merges into trunk.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually I think it would be useful to have it in as "Grammar for GnuCOBOL 3.x", renaming the 3.2 back to 3.1 and adding a new 3.2 (which at least includes the IO_ options and the multiple file handlers). Doing so would actually be a useful documentation what is to be expected with 3.2 (and also what is "missing" with 3.1).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Attached is an update to [r3716]. It covers all changes to be found in 3.1-RC, as well a few that aren't: these extra changes will either be in the final release of 3.1 or in 4.0. Complete details are found in the Changelog.
can you also update the version that is linked on the "Manuals and Guides" page ?
Or better, create a "PDF" folder in the "SVN / CODE ...." folder, save the most recent version of the "grammar.pdf" in this folder and link it in MAnuals and Guides page to the document in the new PDF folder.
In this way we will have the link of grammars.pdf in Manuals and Guides which always points to the latest version.
Same logic as the Programmers Guide manual.
Ciao.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would like to point out a small error in the grammar.
In chapter 8.5 the "rounded-phrase" clause is missing for format 1 of the ADD statement .
Format 2 and format 3 are correct, they have the clause.
See attached screenshot.
Nope according to the Cobol std it is correct as format 1 (simple) a ADD A to B does NOT require or need a giving sub clause and if it did see format 2 (Giving).
In future if you are reporting a bug in software or in a manual please use site's Tickets -> Bugs function to report such.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm sorry to correct you Vincent but I have to repeat what follows:
In chapter 8.5 the "rounded-phrase" clause is missing for format 1 of the ADD statement .
If you compare the grammar with the programmers guide you will see that they are different.
I repeat: for format 1 of the ADD.ì statement
I will also open a bug ticket.
Last edit: Eugenio Di Lorenzo 2020-11-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you very much. One question: do you feel it to be reasonable to specify the current GnuCOBOL version in its title? In many places it more relates to the date, so if you don't mind I'd remove the version number there completely (the relevant parts are in the ChangeLog chapter). What do you think?
I'd also soon move some entries in the ChangeLog, so you woulnd't need an extra commit - just asking because you're the author and I won't adjust the title page without your consent.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've included the version because it indicates what branch I'm basing the manual on, which is trunk, i.e. 4.0-early-dev. Admittedly, the grammar does also include 3.1.1-dev only changes, but this is a hopefully a temporary situation because most of those changes should eventually get merged up to 4.0.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We can place it to the normal download page (manuals and guides linked above), I just wonder why it now lists:
GnuCOBOL 2.2 and then directly skips to GnuCOBOL 3.2 as GnuCOBOL 3.1 is expected to get its release (and the grammar between 3.1 and 3.2-early-dev is still identical [or can be easily made] isn't it?).
I updated the changelog by reading the commit logs for trunk and I got confused when [r3263] turned the Pangea branch into trunk. It looked like 3.1 had been skipped entirely and after [r3263] I skipped all the 3.1 commits that weren't merges into trunk.
Actually I think it would be useful to have it in as "Grammar for GnuCOBOL 3.x", renaming the 3.2 back to 3.1 and adding a new 3.2 (which at least includes the
IO_options and the multiple file handlers). Doing so would actually be a useful documentation what is to be expected with 3.2 (and also what is "missing" with 3.1).I've separated the changelogs in [r3408]. Attached is an updated grammar.
Attached is an update to [r3716]. It covers all changes to be found in 3.1-RC, as well a few that aren't: these extra changes will either be in the final release of 3.1 or in 4.0. Complete details are found in the Changelog.
Hi Edward,
really a wonderful job.
can you also update the version that is linked on the "Manuals and Guides" page ?
Or better, create a "PDF" folder in the "SVN / CODE ...." folder, save the most recent version of the "grammar.pdf" in this folder and link it in MAnuals and Guides page to the document in the new PDF folder.
In this way we will have the link of grammars.pdf in Manuals and Guides which always points to the latest version.
Same logic as the Programmers Guide manual.
Ciao.
As noted before I'll setup a CI build so you'll automatically have the PDFs created without being in svn.
But I'll update the one in the guides page when working on the new website, which will happen in the next weeks.
I would like to point out a small error in the grammar.
In chapter 8.5 the "rounded-phrase" clause is missing for format 1 of the ADD statement .
Format 2 and format 3 are correct, they have the clause.
See attached screenshot.
Last edit: Eugenio Di Lorenzo 2020-11-02
Nope according to the Cobol std it is correct as format 1 (simple) a ADD A to B does NOT require or need a giving sub clause and if it did see format 2 (Giving).
In future if you are reporting a bug in software or in a manual please use site's Tickets -> Bugs function to report such.
I'm sorry to correct you Vincent but I have to repeat what follows:
In chapter 8.5 the "rounded-phrase" clause is missing for format 1 of the ADD statement .
If you compare the grammar with the programmers guide you will see that they are different.
I repeat: for format 1 of the ADD.ì statement
I will also open a bug ticket.
Last edit: Eugenio Di Lorenzo 2020-11-07
On 07/11/2020 16:47, Eugenio Di Lorenzo wrote:
The PG manual is correct so a missive to Edward should sort it out.
On 07/11/2020 16:47, Eugenio Di Lorenzo wrote:
Sorry miss-read your message , changed your bug report to assign to ED
and hign lighted that the grammar doc is wrong and not the PG.
Attached is the Grammar updated to [r3967] and with the error in
ADD(and also inDIVIDE) fixed.Related
Commit: [r3967]
Thank you very much. One question: do you feel it to be reasonable to specify the current GnuCOBOL version in its title? In many places it more relates to the date, so if you don't mind I'd remove the version number there completely (the relevant parts are in the ChangeLog chapter). What do you think?
I'd also soon move some entries in the ChangeLog, so you woulnd't need an extra commit - just asking because you're the author and I won't adjust the title page without your consent.
I've included the version because it indicates what branch I'm basing the manual on, which is trunk, i.e. 4.0-early-dev. Admittedly, the grammar does also include 3.1.1-dev only changes, but this is a hopefully a temporary situation because most of those changes should eventually get merged up to 4.0.