There was the errors which I found in our parser:
* Bug 1.
The parser don't show errors in compilation time when I
write the crt status clause wrongly. In execution, the
function keys don't work.
*> crt status is Tecla.
crt-status is Tecla.
77 Tecla pic 9(004) value
Example programs: parserverbs03.cob
* Bug 2.
The parser don't validating correctly the variable
names. It have leaving pass an cedilla(ç) before any
verbs, as the ACCEPT and DISPLAY verbs.
display "type a valor:" line 11 position 10
accept Field çline 11 çposition 24 auto
Example programs: parserverbs00.cob
* Bug 3.
The parser isn't validating correctly the declared
The parser don't show errors if used the IF verb and I
insert the condition and the value of condition
perform until ws-Exit-True
display "type a valor:" line 11
accept Field çline 11 çposition 24
if Field equal"A" *> Notice that
the string equal"A"
*> is without spaces
set ws-Exit-True to true
Example programs: parserverbs01.cob
* Bug 4.
The Parser isn't requiring the necessary pontuation in
any clauses, as before of a declaration of a label and
in the AUTHOR clause.
In case of AUTHOR clause, sometimes this error cannot
be viewed if the environment division is declared, but
just in case isn´t declared, the errors are showed in
wrong lines, difficulting the error compreention by
author. Hudson Reis (Note que năo tem o ponto
environment division. (Note que năo tem toda a
environment totalmente declarada).
77 Var pic 9(001) value zeros.
Programas exemplo: parserverbs04.cob, parserverbs05.cob
* Bug 5.
The parser isn't validating the correct sintax in to
declare the STOP RUN verb.
O parser năo está validando a sintaxe correta ao se
verbo stop run.
Programas exemplo: parserverbs06.cob,