Hi Marty,
Yes, this behaviour is expected. The change itself was to add syntax checking to >>DEFINE (and other directives); previously, any unexpected words and periods were silently ignored.
I'll open a bug ticket to get the Programmer's Guide to say that periods are not expected in COBOL-2002-style directives.
Edward
On 11 September 2017 at 17:00, <gnucobol-users-request@xxxxxxx> wrote:
...
Message: 1
Date: Mon, 11 Sep 2017 09:36:15 -0400
From: Marty Heyman <mheyman@xxxxxxxxx>
To: gnucobol-users@xxxxxxx
Subject: CDF Behavior Change 2.0 to 2.2
Message-ID: <5E4607BD-08B7-44E3-AEF6-DFA88BEC7A17@xxxxxxxxx >
Content-Type: text/plain; charset=utf-8
Previously, a Compiler Directing Facility DEFINE statement ending with a period (?.?) compiled without error.
In 2.2, the compiler explicitly complains (as an error) that the line ends in a period.
Is this expected behavior? The User?s Guide (2.0) makes no mention of line ending restrictions here.
Thanks.
--
Marty Heyman
Symas Corporation
...
