Tutorial by Topics: t

If you use an IDE and/or build system, it is much easier to set up this kind of project. You create a main application module, then API module, then create a plugin module and make it dependent on the API module or both. Next, you configure where the project artifacts are to be put - in our case t...

The COBOL GENERATE statement is an optional statement supported if the compiler includes the Report Writer feature.

The FREE statement frees allocated memory for one or more identifiers, either by POINTER or from a BASED working storage identifier. Use after FREE is illegal.

The much beloved GO TO. COBOL includes named paragraphs and sections, along with other labels, and any of them can be the target of a GO statement.

Rust has no own framework for GUI development. Yet there are many bindings to existing frameworks. The most advanced library binding is rust-gtk. A 'semi' full list of bindings can be found here

The COBOL GOBACK statement is a return. Unlike EXIT PROGRAM, or STOP RUN, GOBACK always returns one level. If the current module is "main", GOBACK will return to the operating system. If the current module is a subprogram, GOBACK will return to the statement after a call.

The conditional expression and selection statement. Use of explicit scope terminators is recommended. COBOL conditional expressions allow shortforms, where the current identifier (and conditional) is assumed through multiple condition tests, unless explicitly given. IF A = 1 OR 2 ... is equi...

The INITIALIZE statement sets selected data to specified values. Where category-name is:

The INITIATE statement initializes internal Report Writer control fields. Most of a report writer setup occurs in the DATA DIVISION with very brief PROCEDURE DIVISION statements. Once initialized, GENERATE does all the hard work of control break and paging of reports.

The INSPECT statement is a scan and replace verb in COBOL. Where tallying-phrase is: replacing-phrase is: missing image before-after-phrase is:

The MERGE statement will merge one or more like formatted COBOL data files into a single output file. The programmer can assume control over theOUTPUT PROCEDURE, which uses the RELEASE statement, or use internal COBOL runtime mechanisms with the GIVING clause.

Note on using the globbing pattern (**): The globbing pattern matches all children and the parent. In order to avoid that we add '!public' to our del task so that the public directory itself doesn't get deleted