tiny-cobol-users

[Tiny-cobol-users] Preprocessor

[deu439 <de...@az...>]

Hello,
I'am newbie in tiny cobol and i'am looking for something like typedef in
c, is there anything like this?
Also I wanted to ask for tiny cobol preprocessor, how is it running?
Where can I find some documentation about tiny cobol preprocessor?

Thanks for help and sorry for my bad english, i'am not us.

-------------------
de...@in...
Czech Republic

Re: [Tiny-cobol-users] Preprocessor

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

deu439 wrote:

> I'am newbie in tiny cobol and i'am looking for something like typedef in
> c, is there anything like this?

Assuming you mean C structures, '01' levels can be consided to provide 
equivalent functionality (with the C 'pragma pack(1)' directive).

Note that the x86 (IA32) architecture uses a 4 byte boundary alignment.
TC does not use boundary alignment unless the 'SYNC' clause is used.

This can be an issue when reading files and calling C functions from TC.


> Also I wanted to ask for tiny cobol preprocessor, how is it running?
> Where can I find some documentation about tiny cobol preprocessor?

Sorry, no documentation other the source 'pp_parser.y' 'pp_scanner.l' files.

All the preprocessor does is to include copybooks (COPY ..), reformat 
the COBOL sources to free format, remove comments, and print a listing 
if requested.
The output is used as input to the main compiler.

All is run as a single process. The preprocessor is called (see 
process_pp function), after the command line and resource files options 
are processed.

Hint, use the command line '-t' option to see all the intermediate files 
created. The preprocessor output are named '*.i'.

Hope this helps.

Re: [Tiny-cobol-users] Tiny cobol v0.64.0

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

Vince,

I no longer maintain TC.
In my view, resources would be better spent on GCC-COBOL (or what ever
name ...).

In any case, without the COBOL sources, I can only suggest ways on how
to isolate the problem.
So if you can isolate the problem, and assuming that the fix does not
require a major re-write, I will try to update SF CVS with a fix.

Vince Coen wrote:

> Re:
> TinyCOBOL pre-alpha 0.64.0 
> 
> Just put a large M/F program through TC today but it goes into a loop after 
> outputing the source to fn.lis.  All other files are at zero bytes. There are 
> no COPY verb processing as the source file has them included already.

Sounds like a problem with a particular statement (infinite loop), or
maybe a Bison issue (stall).

How to isolate the problem:

First check that the pre-processor output is valid and complete (use the
'-t' or '-E' option).

If the pre-processor output looks valid, then re-build TC using the
following options.

#make uninstall
#make cleandist
#./configure --prefix=/usr --enable-shared=no \
--enable-debug-compiler --with-yacc=yacc193
In the 'compiler/scan.l' file set '#define DEBUG_SCANNER 1'.
#make
#make install

Run TC (htcobol fn.cob | tee trace.txt) and press Control-C to end.


Hope this helps.

PS:
Note that the cause of the Bison stall problem is not known, but can be
removed when TC is compiled with Berkeley's YACC (preferably version
1.9.3).