-
Notifications
You must be signed in to change notification settings - Fork 25
HowToTest
Parse our Cobol 85 programs and generate them to Cobol 85. Then compare the AST of the original source and the generated to check if they match. Use another parser to compare result.
Compare our SymbolTable with an ADATA file. Try to compare our syntactic and semantic error with IBM Compiler.
Convert one of our legacy application to TypeCobol and ensure it pass qualification tests. Compare performance of this legacy app in Cobol 85 and in TypeCobol. Compare memory consumption. Measure time needed to rewrite our legacy app to TypeCobol. Measure the number of line of code before and after.
Use Abend-Aid and Xpediter with a TypeCobol program to be sure that it works.
Run all our unit tests.
Create a Cobol 85 program which call the generated call.
Convert Cobol 85 programs to TC. Call them with parameters. Call corresponding Cobol 85 programs with the same parameters and check if the output is the same.
Develop a unit test framework in TC.
Make a batch which extract data from different sources. Make this batch in Cobol 85 and in TC and check the result. The file must match. Also compare their performance.
Introduction
TypeCobol language
-
In a nutshell
-
TypeCobol concepts
TypeCobol Editor
(Type)Cobol parser API
TypeCobol architecture
- Glossary
- Main phases
- How to extend the grammar and semantic check (full example)
- File
- Text
- Code analysis steps
- Program class parser
- Type checker
- Error handler
- Grammars Composition
- Code generation
- Compilation process
(Type)Cobol concepts / reference doc
Contributing