Re: [Tiny-cobol-users] MicroFocus Compatibility option

[David E. <de...@us...>]

Carlos Gomes wrote:

> How do I know MF features associated with option
> --enable-mfcomp when I generate htcobol with this option???

There are only two options which must be explicitly enabled when TC is 
configured.

COMMAND-LINE:
The statement 'ACCEPT identifier-1 FROM COMMAND-LINE' will retrieve the 
command-line arguments and place them in identifier-1, delimited by spaces.
The TC default is to use the UN*X like feature and include the first 
argument, the actual external name (binary) of the calling program.
With the 'mfcomp' option, the external name (binary) is omitted.

example (default):
$prog1.exe a b c -> 'prog1.exe a b c'

example (mfcomp):
$prog1.exe a b c -> 'a b c'


See 'test.code/t17' directory for an example.

EXTERN-FILE:
SELECT ... ASSIGN TO EXTERNAL [ literal-1 | identifier-1 ]

The EXTERNAL clause of the 'SELECT' statement enables the association
of internal file identifiers with external file names, and is achieved 
by the use of environment variables.
This feature mimics the methodology found on main-frames.
The TC default is to use identifier (or literal) and use it to search 
for the environment variable. If the environment variable is found, use 
the name as the actual file name.
With the 'mfcomp' option, the search sequence is more complex and a 
'DD_' prefix is used. It basically mimics the methodology found in MF 
compilers.
See 'fileio.c' file for details.

example (default):
$export SYS002=/home/user123/filein1
...
SELECT filein1 ASSIGN TO EXTERNAL "SYS002"
then ...
filein1=/home/user123/filein1

See 'test.code/t19' directory for an example.

Perhaps a better approach would be to add these as run-time options, 
which could then be defined by the user.