Hi Vincent
1) under 7.8.1.4 ACCEPT data-item you wrote:
[ BLINK ] [ HIGHLIGHT | LOWLIGHT ] [ REVERSE-VIDEO ] REVERSE | REVERSED ]
but there is a wrong ] between REVERSE-VIDEO and REVERSE.
The correct diagram is:
[ BLINK ] [ HIGHLIGHT | LOWLIGHT ] [ REVERSE-VIDEO | REVERSE | REVERSED ]
2) and you wrote:
ON EXCEPTION|ESCAPE imperative-statement-1 ]
~~~~~~~~~ ~~~~~
This means you can code ESCAP instead of ESCAPE, please cprrect as:
ON EXCEPTION|ESCAPE imperative-statement-1 ]
~~~~~~~~~ ~~~~~~
I kindly suggest to copy and paste from the files I send to avoid typing errors.
There's another typo in the programmer's guide related to TEST-DAY-YYYYDDD:
8.1.95 TEST-DAY-YYYYDDD
TEST-DAY-YYYYDDD Function Syntax
TEST-DATE-YYYYDDD(date) << error, only TEST-DAY-YYYYDDD works...
~~~~~~~~~~~~~~~~~
————————————————————————————————————————
This function determines if the supplied date (a numeric integer data item or literal) is a
valid date.
A valid date is one of the form yyyyddd in the range 1601001 to 9999365. Leap year is
accounted for in determining the maximum number of days in a year.
If the date is valid, a 0 value is returned. If it isn’t, a value of 1 or 2 is returned signalling
the problem lies with the year or day, respectively.
3 December
Eugenio, I can not copy / paste as your char positioning is off but done.
Arnold This tests against value in date so the element (date) must be present ?
Otherwise what is it testing ?
Eugenio, I can not copy / paste as your char positioning is off.
Arnold This tests against value in date so the element (date) must be present ?
Otherwise what is it testing ?
The name of the function is TEST-DAY-YYYYDDD and it works fine, but in the manual it is incorrectly spelled as TEST-DATE-YYYYDDD in the syntax example only. In the chapter title and header the function name is correctly spelled as TEST-DAY-YYYYDDD
There is a separate function named TEST-DATE-YYYYMMDD which works fine and the manual appears to be correct where it is described.
This is not an urgent problem, but if you're making a lot of changes to the manuals, it should be easy to include.
Kind regards
I'm sorry to hear that the character positioning is wrong.
I was careful about this, just to make your work easier.
Can you give me an example?
So that next time the character positioning will be correct.
Unless you look at the sources you will not spot the indentations but please do so if you can.
Here is the sources :
https://sourceforge.net/p/gnucobol/code/HEAD/tree/external-doc/guide/
OK, understand now - all fixed and added a space between func. names and vars.