KNOWN BUGS

conditional Statement of type '( A + 12 ) = 100 ' not handled properly
Embedded SQL - Host variables not printed
Stability problems ... calling Lisp Procedure while Unsafe ... resolved
translation of 88 Variable definitions - previously always printed as conditional, now tidied up
Java - string comparisons in generated code using 'compareTo' is too cumbersome ...Moving Data to GROUP-DATA -> field alignment is slightly out
SELECT file ASSIGN TO PRINTER. - failes during code generation
FILE-CONTROL: SELECT ... ALTERNATIVE KEY var1 FOR var2 var3 var4 ...
Java SQL Libraries (ACMQUery) - need further tuning
File-status information currently not always translated properly
MFCobol SCREEN SECTION. - Lines with no variable entries Fail.
COBOL INSPECT Statement Parsed but not properly handled yet
partly REDEFINES fields/groups
MULTI PROCEDURE DIVISION - java code needs modifications
Saving processed record structures - misses out on some of the datafiles -
Multi-procedure Cobol programs. COPIED FD file not visible in all the PROCS.
Delphi RUN Procedure declaration , semi-colons missing - when passing parameters
Reports - Printer files -> in user-inc the files are incorrectly named
Data-type conversions occasionally missed out on arrays.
INSPECT var TALLYING var2 FOR LEADING var2 -- for Leading section fails parser
COBOL Merge statements not handled yet
Field items with no field definitions - field-length defaults to 2 places, should default to 0
Parser - Multiple arithmatic operations within one statement causes parser to fail
MOVE spaces to ARRAYED-GROUP
Parsing POWER function (**) - incorrect parsing when the first argument is bracketed ...
Lexical Analysers : Need to ensure the '=' is padded.
COPY filename . . -> The second fullstop will confuse the lexical analyser !
78 types in Data Description entry - should really be translated to constants rather than variables

conditional Statement of type '( A + 12 ) = 100 ' not handled properly

Embedded SQL - Host variables not printed

Stability problems ... calling Lisp Procedure while Unsafe ... resolved

translation of 88 Variable definitions - previously always printed as conditional, now tidied up

Java - string comparisons in generated code using 'compareTo' is too cumbersome ...

Moving Data to GROUP-DATA -> field alignment is slightly out

SELECT file ASSIGN TO PRINTER. - failes during code generation
Although the following will execute successfully
   SELECT file ASSIGN TO PRINTER "filename".

FILE-CONTROL: SELECT ... ALTERNATIVE KEY var1 FOR var2 var3 var4 ...

Java SQL Libraries (ACMQUery) - need further tuning

File-status information currently not always translated properly
Currently the only time that we are looking for file-status is
IF FILE-STATUS = "00" then ....
this is not completely correct either.

MFCobol SCREEN SECTION. - Lines with no variable entries Fail.
Parser section fails on variable definitions with no variable names (used in MF COBOL Screen Section).
01 abcd .
03 LINE 3 . <<<---- Fails here.
04 LINE "a string" .
SOLUTION
===============
Modify your program and enter a vaiable name on that line !

COBOL INSPECT Statement Parsed but not properly handled yet

partly REDEFINES fields/groups

MULTI PROCEDURE DIVISION - java code needs modifications

Saving processed record structures - misses out on some of the datafiles -

Multi-procedure Cobol programs. COPIED FD file not visible in all the PROCS.

Delphi RUN Procedure declaration , semi-colons missing - when passing parameters
eg
procedure run(Sender: Tcomponent; P_Lk_Ppaccx: TLK_ppaccx P_Lk_Pplinkag: TLK_pplinkag);
*****************************************************************************^
However, in the actual declaration (later on in the program) everything is ok.

Reports - Printer files -> in user-inc the files are incorrectly named

Data-type conversions occasionally missed out on arrays.
Occasionally the conversion of array date types is omitted, eg the Cobol statemente
    MOVE string_variable1 TO arrayed_integer_variable (n)
is currently translated to
    arrayed_integer_variable (n) := string_variable1;
Instead of
arrayed_integer_variable (n) := strtoint(string_variable1);

INSPECT var TALLYING var2 FOR LEADING var2 -- for Leading section fails parser

COBOL Merge statements not handled yet

Field items with no field definitions - field-length defaults to 2 places, should default to 0

Parser - Multiple arithmatic operations within one statement causes parser to fail
eg
:MULTIPLY a BY b ROUNDED c
d

MOVE spaces to ARRAYED-GROUP
eg 03 abcd occurs 10 times .
04 xxx pic "99".
Move spaces to abcd will become:

Parsing POWER function (**) - incorrect parsing when the first argument is bracketed ...
eg.
    COMPUTE A = ( (B + 5 ) ** -6 )
will then be translated to
    A = BMath.pow(, -6)));
instead of

Lexical Analysers : Need to ensure the '=' is padded.

COPY filename . . -> The second fullstop will confuse the lexical analyser !

78 types in Data Description entry - should really be translated to constants rather than variables