Menu
▾
▴
tiny-cobol-users
You can subscribe to this list here.
| 1999 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(341) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2000 |
Jan
(42) |
Feb
(22) |
Mar
(59) |
Apr
(12) |
May
(15) |
Jun
(30) |
Jul
(25) |
Aug
(13) |
Sep
(98) |
Oct
(51) |
Nov
(95) |
Dec
(99) |
| 2001 |
Jan
(105) |
Feb
(175) |
Mar
(411) |
Apr
(310) |
May
(294) |
Jun
(213) |
Jul
(132) |
Aug
(82) |
Sep
(26) |
Oct
(121) |
Nov
(181) |
Dec
(96) |
| 2002 |
Jan
(52) |
Feb
(128) |
Mar
(141) |
Apr
(111) |
May
(149) |
Jun
(164) |
Jul
(33) |
Aug
(77) |
Sep
(62) |
Oct
(92) |
Nov
(14) |
Dec
(33) |
| 2003 |
Jan
(33) |
Feb
(58) |
Mar
(120) |
Apr
(180) |
May
(206) |
Jun
(110) |
Jul
(232) |
Aug
(207) |
Sep
(103) |
Oct
(122) |
Nov
(42) |
Dec
(68) |
| 2004 |
Jan
(83) |
Feb
(107) |
Mar
(90) |
Apr
(7) |
May
(42) |
Jun
(36) |
Jul
(11) |
Aug
(24) |
Sep
(67) |
Oct
(116) |
Nov
(96) |
Dec
(22) |
| 2005 |
Jan
(29) |
Feb
(6) |
Mar
(12) |
Apr
(31) |
May
(47) |
Jun
(12) |
Jul
(76) |
Aug
(69) |
Sep
(7) |
Oct
(21) |
Nov
(5) |
Dec
(4) |
| 2006 |
Jan
(5) |
Feb
(7) |
Mar
(7) |
Apr
(3) |
May
(4) |
Jun
(4) |
Jul
(8) |
Aug
(13) |
Sep
(7) |
Oct
(2) |
Nov
(6) |
Dec
(30) |
| 2007 |
Jan
(43) |
Feb
(7) |
Mar
(2) |
Apr
(4) |
May
(11) |
Jun
(1) |
Jul
|
Aug
|
Sep
(22) |
Oct
(18) |
Nov
(6) |
Dec
(31) |
| 2008 |
Jan
(1) |
Feb
(2) |
Mar
(3) |
Apr
|
May
|
Jun
(3) |
Jul
(1) |
Aug
(2) |
Sep
(2) |
Oct
(11) |
Nov
(8) |
Dec
|
| 2009 |
Jan
(6) |
Feb
(4) |
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
(3) |
Nov
|
Dec
(8) |
| 2010 |
Jan
(15) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(4) |
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
(12) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
(7) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Zoran S. <zrn...@ya...> - 2009-12-14 20:37:14
|
-
Carlucio Lopes
I believe that the example on which the speech was interesting and others.
Thank you.
|
|
From: Carlucio L. <car...@te...> - 2009-12-08 00:26:32
|
John Culleton you will need to install tinycobol and apache this server, with all the libraries, I am sending you an email with sources and examples for installation. unfortunately this will be in Portuguese but easy to understand. -- Carlucio Lopes - 62-8415-8939 msn: car...@ho... http://www.tinycobol.org http://www.debian.org http://www.postgresql.org |
|
From: David E. <de...@us...> - 2009-12-07 23:32:00
|
RFC (Request For Comment): The current TC CVS version (0.64.67), seams to be relatively stable and ready for testing. To download use CVS and follow the download instructions found here [1]. Just change 'modulename' to 'development'. Lots of changes to the file IO compiler and run-time have been made. Variable length file support has improved and added for relative and indexed files. Indexed file IO now uses VB-ISAM version 2 (a C-IS*M clone of sorts). BDB is no longer used for indexed files. It is still required by the RT for SORT. Some NOTES: VB-ISAM is not usually included in any UN*X distributions. So needs to be build from source, which can be found on the TC files section on SF [2]. File IO code generation is not compatible with previous versions. While accessing (LINE) SEQUENTIAL files created by previous TC versions should work, accessing RELATIVE or INDEXED files is NOT recommended. Any shared libraries created using previous versions TC should be recompiled. Win32 users (MinGW and Cygwin), need to run 'tconfig.mingw.sh' shell script to generate the make files. Cygwin users should change the prefix from "C:/MinGW" to "/", or cygwin-drive. While 64-bit systems should run 32-bit applications, no tests have been performed. While TC-Win32 should run on winVista and win7, no tests have been performed. Anyway enjoy. As usual any comments and PIZZA coupons are welcomed. 1) CVS instructions: http://sourceforge.net/projects/tiny-cobol/develop 2) ISAM - vbisam-2.0.tar.bz2 http://sourceforge.net/projects/tiny-cobol/files/ |
|
From: John C. <jo...@we...> - 2009-12-07 15:30:58
|
On Sunday 06 December 2009 21:29:22 David Essex wrote: > All that is required is the TC run-time library and resource file > 'htrtconf'. But it is probably easier to install TC (RT and compiler). > As it happens, it isn't. I only have limited access to the remote site via ftp. I'll try moving the rtl and htrtconf to cgi-bin and see if that works. Thanks for your help. -- John Culleton "Create Book Covers with Scribus" http://www.booklocker.com/books/4055.html |
|
From: John C. <jo...@we...> - 2009-12-07 14:18:44
|
On Sunday 06 December 2009 20:30:10 you wrote: > On Sat, 5 Dec 2009 17:29:49 -0500 > > John Culleton <jo...@we...> wrote: > > I want to run Tiny-Cobol programs on a remote Linux website. > > Obviously the application program itself must be compiled and > > copied over to the remote site. But what else is required in the way > > of libraries etc. on the remote site? > > > > This is a cgi type application. > > > > -- > > John Culleton > > atached Thanks for your extended examples of CGI programs using Tiny Cobol. That document provides part of the solution. I don't understand Portugese but I do understand Cobol and HTML! Now the next question is, what files must I transport to my remote web site on doteasy.com to allow the Cobol program to run? I have access on that site to only a limited subset of the facilities of Linux. But I can transport html files and cgi type files. I am reasonably certain that the site does not have a Cobol compiler installed. I am also reasonably certain that I can not install a compiler on it. But I can put files in the following directories: /home /tmp /var/www /var/www/cgi-bin /var/www/html /var/www/perl I can also create subdirectories to these. Thus far I have been successful with perl and Tcl as cgi-bin programs. The key question is: what files do I need to sent to this site beyond my compiled Cobol program. e.g. foo.exe? Is it possible to compile a static .exe file? -- John Culleton 2401 Haight Avenue Eldersburg MD 21784 410-795-1159 |
|
From: David E. <de...@us...> - 2009-12-07 03:14:03
|
All that is required is the TC run-time library and resource file 'htrtconf'. But it is probably easier to install TC (RT and compiler). All dependencies (ncurses, BDB) are linked to the TC run-time library, and are loaded at run-time. You can check all dependencies by using the LDD command utility (ldd libhtcobol.so ...). Unless both systems use the same Linux distribution version, it would be prudent to build and install both TC and the application programs on the remote Linux system. John Culleton wrote: > I want to run Tiny-Cobol programs on a remote Linux website. > Obviously the application program itself must be compiled and > copied over to the remote site. But what else is required in the way > of libraries etc. on the remote site? > > This is a cgi type application. Hope this helps. |
|
From: John C. <jo...@we...> - 2009-12-06 00:26:19
|
I want to run Tiny-Cobol programs on a remote Linux website. Obviously the application program itself must be compiled and copied over to the remote site. But what else is required in the way of libraries etc. on the remote site? This is a cgi type application. -- John Culleton |
|
From: David E. <de...@us...> - 2009-10-30 16:54:49
|
TC generates 32-bit GNU assembler (GAS). And you are trying to build it using a 64-bit compiler. I'm not familiar with 64-bit systems, so I can't help you. Carlucio Lopes wrote: > I am with problem below, somebody could help me? > > $gcc -v > Using built-in specs. > Target: x86_64-suse-linux > ... > gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) > > $as -V > GNU assembler version 2.19 (x86_64-suse-linux) using BFD version (GNU > Binutils; openSUSE 11.1) 2.19 > > $htcobol -V > TinyCOBOL - pre alpha 0.62.0 (linux-gnu 2009/10/29) > (C) 1991, 1993, 1999-2003 Rildo Pragana et. al. > > $htcobol -c -F -P af001.cob > af001.s: Assembler messages: > af001.s:10: Error: suffix or operands invalid for `push' > af001.s:17: Error: suffix or operands invalid for `push' > af001.s:18: Error: suffix or operands invalid for `push' > af001.s:20: Error: suffix or operands invalid for `push' > af001.s:28: Error: suffix or operands invalid for `push' > af001.s:30: Error: suffix or operands invalid for `push' > af001.s:32: Error: suffix or operands invalid for `push' > |
|
From: Guillaume Y. <gui...@ci...> - 2009-10-29 17:21:45
|
Carlucio Lopes a écrit :
> I am with problem below, somebody could help me?
Hello.
I haven't tried compiling tinycobol yet, but the webpage states that
tinycobol works on i386. It seems to me that you're using an amd64
platform. Assembly code is therefore not tailored to your platform.
Maybe you could try to run it with linux32 or something like that...
By the way, just a suggestion: since amd64 will become more popular, why
not try to compile cobol files to bytecode, and not native code?
All the best,
--
Guillaume Yziquel
http://yziquel.homelinux.org/
|
|
From: Carlucio L. <car...@te...> - 2009-10-29 10:32:14
|
I am with problem below, somebody could help me? $gcc -v Using built-in specs. Target: x86_64-suse-linux Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.3 --enable-ssp --disable-libssp --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --disable-libgcj --disable-libmudflap --with-slibdir=/lib64 --with-system-zlib --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --program-suffix=-4.3 --enable-linux-futex --without-system-libunwind --with-cpu=generic --build=x86_64-suse-linux Thread model: posix gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) $as -V GNU assembler version 2.19 (x86_64-suse-linux) using BFD version (GNU Binutils; openSUSE 11.1) 2.19 $htcobol -V TinyCOBOL - pre alpha 0.62.0 (linux-gnu 2009/10/29) (C) 1991, 1993, 1999-2003 Rildo Pragana et. al. $htcobol -c -F -P af001.cob af001.s: Assembler messages: af001.s:10: Error: suffix or operands invalid for `push' af001.s:17: Error: suffix or operands invalid for `push' af001.s:18: Error: suffix or operands invalid for `push' af001.s:20: Error: suffix or operands invalid for `push' af001.s:28: Error: suffix or operands invalid for `push' af001.s:30: Error: suffix or operands invalid for `push' af001.s:32: Error: suffix or operands invalid for `push' -- Carlucio Lopes - 62-8415-8939 msn: car...@ho... http://www.tinycobol.org http://www.debian.org http://www.postgresql.org |
|
From: David E. <de...@us...> - 2009-08-12 07:36:45
|
W. Burke Cabaniss wrote: > ... > Assembler or C now fails with many hundred "suffix or operands > invalid for push|pop". I assume this relates to a gcc change, and > just want to update htcobol. I assume many changes and fixes. Negleted to mention that TC generates 32-bit GNU assembler. So if your system is 64-bit, then TC with the current setup, will not work. Cheers. |
|
From: David E. <de...@us...> - 2009-08-12 05:54:06
|
W. Burke Cabaniss wrote: > I installed htcobol many years ago; cannot determine old version > because no such option under `htcobol -h`, and not on any listings. > It worked fine for me. You can determine the version number by 'htcobol -V'. > Assembler or C now fails with many hundred "suffix or operands > invalid for push|pop". I assume this relates to a gcc change, and > just want to update htcobol. I assume many changes and fixes. No idea as to why this is happening. Note that TC 0.64 has not been tested with GCC 4x. > Have downloaded and compiled tinycobol-0.64 - NO, configure says > db.h missing; several similar messages. Have studied faq-libdb.html > from tinycobol web page, downloaded db1-1.85.4-8.i386.rpm and > installed it with `rpm -ivvh` many times. I've rpm'ed the src.rpm > too. No error messages but `whereis libdb` fails. Your system is RPM based, so BDB is installed by default. The TC BDB configuration failed. A common problem. Note that installing old versions of BDB on RPM based systems, can cause problems. > I know COBOL language, not C compile or libraries at all. I see > db.h in source. I assume there is no executable module. Please > correct my misunderstanding, suggest a fix, or a redirection. The only thing I can suggest is to try to build TC 0.64 from the sources. Example: ./configure --prefix=/usr --with-libdb=3 make make install # as root make uninstall # To remove TC First try to configure TC with the '--with-libdb=ARG (ARG=1,2,3,4)' option. Example: ./configure --prefix=/usr --with-libdb=3 If the above example fails, then try 4 and 2. If the configure works, the build the source, type 'make'. If the build works, fix a bug to the 'compiler/Makefile' file. Bug fix: ... #install: install-rts-config install: install-rts-config install-static-libs install-shared-libs ... #uninstall: uninstall-rts-config uninstall: uninstall-rts-config uninstall-static-libs uninstall-shared-libs # One line Remove the old versions of TC binaries, run-time and configuration files, as they can cause problems. Install TC, 'make install', as root (or sudo). Update the UN*X loader cache, 'ldconfig' as root (or sudo). Now try a test compile (htcobol -v helloWorld.cob). Some examples can be found in the 'test.code' directories. Hope this helps. |
|
From: W. B. C. <bu...@bs...> - 2009-08-11 21:52:59
|
I installed htcobol many years ago; cannot determine old version because no such option under `htcobol -h`, and not on any listings. It worked fine for me. Assembler or C now fails with many hundred "suffix or operands invalid for push|pop". I assume this relates to a gcc change, and just want to update htcobol. I assume many changes and fixes. Have downloaded and compiled tinycobol-0.64 - NO, configure says db.h missing; several similar messages. Have studied faq-libdb.html from tinycobol web page, downloaded db1-1.85.4-8.i386.rpm and installed it with `rpm -ivvh` many times. I've rpm'ed the src.rpm too. No error messages but `whereis libdb` fails. I know COBOL language, not C compile or libraries at all. I see db.h in source. I assume there is no executable module. Please correct my misunderstanding, suggest a fix, or a redirection. |
|
From: David E. <de...@us...> - 2009-05-27 00:56:44
|
Sorry, wrong list. David Essex wrote: > Jeff Chimene wrote: > > > >>That's certainly the approach I'd take if I >>was starting from scratch. > > > Well, actually NOT from scratch. > You have a scanner/parser, run-time, syntax tree. > I would say about 40-50% complete. Over optimistic ? Maybe. > > In any case I think it can be done, with the proper sponsor, financing. > > > > The biggest hurdle I see is official incorporation into GCC. > > Perhaps that's not as big a hurdle as it seems. > > Not likely to happen any time soon. > But then again, other compilers use the GCC back-end. > Some, such as GCC-Pascal, eventually became part of GCC (FSF supported > projects). > > > >>On the debugging side, here is another possible approach. It's >>basically the one that's appeared in various guises in this thread: >>http://www.mono-project.com/Debugging >> >>Ignoring the JIT stuff, it would seem that cobc is well on the way to >>supporting the necesary call-backs as demonstrated by those Python >>data dump routines. >> >>Given the wealth of scripting languages supported by OC, it's really a >>matter of designing and implementing useful COBRTL routines for them >>to call. >> >>COBOL_OC_DUMP is certainly useful. > > > Which ever approach chosen, you still have to find a way to pass > debugging information (COBOL->C->binary-object). > No small task, I don't think. > > Perhaps the simplest possible approach is to add 'READY/RESET TRACE' > COBOL extension. In combination with 'DISPLAY', it is a good tool for > debugging classic type COBOL programs. > > > Cheers. |
|
From: David E. <de...@us...> - 2009-05-26 21:53:20
|
Jeff Chimene wrote: > ... > That's certainly the approach I'd take if I > was starting from scratch. Well, actually NOT from scratch. You have a scanner/parser, run-time, syntax tree. I would say about 40-50% complete. Over optimistic ? Maybe. In any case I think it can be done, with the proper sponsor, financing. > The biggest hurdle I see is official incorporation into GCC. > Perhaps that's not as big a hurdle as it seems. Not likely to happen any time soon. But then again, other compilers use the GCC back-end. Some, such as GCC-Pascal, eventually became part of GCC (FSF supported projects). > On the debugging side, here is another possible approach. It's > basically the one that's appeared in various guises in this thread: > http://www.mono-project.com/Debugging > > Ignoring the JIT stuff, it would seem that cobc is well on the way to > supporting the necesary call-backs as demonstrated by those Python > data dump routines. > > Given the wealth of scripting languages supported by OC, it's really a > matter of designing and implementing useful COBRTL routines for them > to call. > > COBOL_OC_DUMP is certainly useful. Which ever approach chosen, you still have to find a way to pass debugging information (COBOL->C->binary-object). No small task, I don't think. Perhaps the simplest possible approach is to add 'READY/RESET TRACE' COBOL extension. In combination with 'DISPLAY', it is a good tool for debugging classic type COBOL programs. Cheers. |
|
From: Carlucio L. <car...@te...> - 2009-02-28 16:32:47
|
On Sat, 28 Feb 2009 00:01:01 -0500 David Essex <de...@us...> wrote: > I do not think 'EXIT PARAGRAPH' is part of COBOL-85 standard. > > The COBOL 200x standard states as follows. > > EXIT [ PROGRAM | PARAGRAPH | SECTION | METHOD | FUNCTION | PERFORM ]. > > So it is probably a MF extention to the COBOL-85 standard. > > However, it seems to be functionally equivalent. > So I have updated SF CVS (version 0.64.7) with your changes. thanks, -- Carlucio Lopes-Cobolito 62-8415-8939 Tinycobol/Debian Gnu-Linux/Postgresql Novo Link PIRATARIA ENTENDA ->> http://carlinux.no-ip.info:81 |
|
From: vince c. <vb...@bt...> - 2009-02-28 11:07:06
|
According to my MF manual, Paragraph is a MF extention in a docuement that
has defs for 74, 85 and other standards listed.
(Micro Focus Cobol Language reference issue 13 April 93).
Vince
On Saturday 28 February 2009, David Essex wrote:
> I do not think 'EXIT PARAGRAPH' is part of COBOL-85 standard.
>
> The COBOL 200x standard states as follows.
>
> EXIT [ PROGRAM | PARAGRAPH | SECTION | METHOD | FUNCTION | PERFORM ].
>
> So it is probably a MF extention to the COBOL-85 standard.
>
> However, it seems to be functionally equivalent.
> So I have updated SF CVS (version 0.64.7) with your changes.
>
> Carlucio Lopes wrote:
> > Comando : EXIT PARAGRAPH
> > Para adquar o padrao STD85 MF solicito a sequinte alteracao:
> >
> > arquivo htcobol.y
> > de:
> > %token ORGANIZATION OTHER OUTPUT OVERFLOW_TOK
> > %token PADDING PAGE PAGE_COUNTER PERFORM PF PH PICTURE PLUS POINTER
> > POSITION %token POSITIVE PREVIOUS PROCEDURE PROCEED PROGRAM PROGRAM_ID
> > ...
> > ..
> > /* EXIT statement */
> > exit_statement:
> > EXIT { gen_exit(0); }
> >
> > | EXIT PROGRAM { gen_exit(1); }
> >
> > ;
> >
> > para:
> > %token ORGANIZATION OTHER OUTPUT OVERFLOW_TOK
> > %token PADDING PAGE PAGE_COUNTER PARAGRAPH PERFORM PF PH PICTURE PLUS
> > POINTER POSITION %token POSITIVE PREVIOUS PROCEDURE PROCEED PROGRAM
> > PROGRAM_ID
> > ...
> > ...
> > /* EXIT statement */
> > exit_statement:
> > EXIT { gen_exit(0); }
> >
> > | EXIT PARAGRAPH { gen_exit(0); }
> > | EXIT PROGRAM { gen_exit(1); }
> >
> > ;
> >
> > arquivo reswords.c :
> > de:
> > {"PAGE-COUNTER", PAGE_COUNTER, 0, TCOB_KW_STD},
> > {"PERFORM", PERFORM, 0, TCOB_KW_STD},
> > {"PF", PF, 0, TCOB_KW_STD},
> >
> > para:
> > {"PAGE-COUNTER", PAGE_COUNTER, 0, TCOB_KW_STD},
> > {"PARAGRAPH", PARAGRAPH, 0, TCOB_KW_STD85},
> > {"PERFORM", PERFORM, 0, TCOB_KW_STD},
> > {"PF", PF, 0, TCOB_KW_STD},
> >
> >
> > veja programa abaixo:
> > identification division.
> > program-id. paragraph01.
> > author. Carlucio Lopes.
> > environment division.
> > configuration section.
> > special-names.
> > decimal-point is comma.
> > data division.
> > working-storage section.
> > 77 wsn-parag pic 9(01).
> > 88 wsc-parag-ok value 1 2 3.
> > procedure division.
> > move 1 to wsn-parag
> > perform until wsn-parag = zero
> > evaluate wsn-parag
> > when 01 perform 000-parag
> > when 02 perform 010-parag
> > when 03 perform 020-parag
> > when other move zero to wsn-parag
> > end-evaluate
> > end-perform
> > stop run.
> > 000-parag.
> > display "000-parag " at 0910
> > accept wsn-parag at 1010
> > if not wsc-parag-ok
> > display "Sai do programa" at 1110 stop " "
> > exit paragraph
> > end-if
> > display "000-parag sai " at 1210.
> > 010-parag.
> > display "010-parag " at 0910
> > accept wsn-parag at 1010
> > if not wsc-parag-ok
> > display "Sai do programa" at 1110 stop " "
> > exit paragraph
> > end-if
> > display "010-parag sai " at 1210.
> > 020-parag.
> > display "020-parag " at 0910
> > accept wsn-parag at 1010
> > if not wsc-parag-ok
> > display "Sai do programa" at 1110 stop " "
> > exit paragraph
> > end-if
> > display "020-parag sai " at 1210.
> >
> >
> > carlucio@carlinux:~$ htcobol -x -F -P paragraph01.cob
> > paragraph01.cob: 28: error: syntax error, on or before 'paragraph'
> > paragraph01.cob: 28: error: unknown or wrong statement, on or before
> > 'paragraph'
> > paragraph01.cob: 28: error: unknown or wrong statement, on or before
> > 'paragraph'
> > paragraph01.cob: 29: error: unknown or wrong statement, on or before
> > 'end-if'
> > paragraph01.cob: 35: error: syntax error, on or before 'paragraph'
> > paragraph01.cob: 35: error: unknown or wrong statement, on or before
> > 'paragraph'
> > paragraph01.cob: 35: error: unknown or wrong statement, on or before
> > 'paragraph'
> > paragraph01.cob: 36: error: unknown or wrong statement, on or before
> > 'end-if'
> > paragraph01.cob: 42: error: syntax error, on or before 'paragraph'
> > paragraph01.cob: 42: error: unknown or wrong statement, on or before
> > 'paragraph'
> > paragraph01.cob: 42: error: unknown or wrong statement, on or before
> > 'paragraph'
> > paragraph01.cob: 43: error: unknown or wrong statement, on or before
> > 'end-if'
> > carlucio@carlinux:~$
> >
> > com a alteracao:
> > carlucio@carlinux:~$ htcobol -x -F -P paragraph01.cob
> >
> > compilou ok.
>
> ---------------------------------------------------------------------------
>--- Open Source Business Conference (OSBC), March 24-25, 2009, San
> Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing
> the Enterprise -Strategies to boost innovation and cut costs with open
> source participation -Receive a $600 discount off the registration fee with
> the source code: SFAD http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Tin...@li...
> https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users
--
IMPORTANT – This email and the information in it may be confidential, legally
privileged and/or protected by law. It is intended solely for the use of the
person to whom it is addressed. If you are not the intended recipient, please
notify the sender immediately and do not disclose the contents to any other
person, use it for any purpose, or store or copy the information in any
medium. Please also delete all copies of this email and any attachments from
your system.
We cannot guarantee the security or confidentiality of email communications.
We do not accept any liability for losses or damages that you may suffer as a
result of your receipt of this email including but not limited to computer
service or system failure, access delays or interruption, data non-delivery
or mis-delivery, computer viruses or other harmful components.
Copyright in this email and any attachments belongs to Applewood Computers.
Should you communicate with anyone at Applewood Computers by email, you
consent to us monitoring and reading any such correspondence.
Nothing in this email shall be taken or read as suggesting, proposing or
relating to any agreement concerted practice or other practice that could
infringe UK or EC competition legislation.
Dykegrove Limited T/A Applewood Computers is a company registered in England
and Wales (number 01681349) whose registered office is at Applewood House,
Epping Road, Roydon, Essex, CM19 5DA
|
|
From: David E. <de...@us...> - 2009-02-28 05:02:41
|
I do not think 'EXIT PARAGRAPH' is part of COBOL-85 standard.
The COBOL 200x standard states as follows.
EXIT [ PROGRAM | PARAGRAPH | SECTION | METHOD | FUNCTION | PERFORM ].
So it is probably a MF extention to the COBOL-85 standard.
However, it seems to be functionally equivalent.
So I have updated SF CVS (version 0.64.7) with your changes.
Carlucio Lopes wrote:
> Comando : EXIT PARAGRAPH
> Para adquar o padrao STD85 MF solicito a sequinte alteracao:
>
> arquivo htcobol.y
> de:
> %token ORGANIZATION OTHER OUTPUT OVERFLOW_TOK
> %token PADDING PAGE PAGE_COUNTER PERFORM PF PH PICTURE PLUS POINTER POSITION
> %token POSITIVE PREVIOUS PROCEDURE PROCEED PROGRAM PROGRAM_ID
> ...
> ..
> /* EXIT statement */
> exit_statement:
> EXIT { gen_exit(0); }
> | EXIT PROGRAM { gen_exit(1); }
> ;
>
> para:
> %token ORGANIZATION OTHER OUTPUT OVERFLOW_TOK
> %token PADDING PAGE PAGE_COUNTER PARAGRAPH PERFORM PF PH PICTURE PLUS POINTER POSITION
> %token POSITIVE PREVIOUS PROCEDURE PROCEED PROGRAM PROGRAM_ID
> ...
> ...
> /* EXIT statement */
> exit_statement:
> EXIT { gen_exit(0); }
> | EXIT PARAGRAPH { gen_exit(0); }
> | EXIT PROGRAM { gen_exit(1); }
> ;
>
> arquivo reswords.c :
> de:
> {"PAGE-COUNTER", PAGE_COUNTER, 0, TCOB_KW_STD},
> {"PERFORM", PERFORM, 0, TCOB_KW_STD},
> {"PF", PF, 0, TCOB_KW_STD},
>
> para:
> {"PAGE-COUNTER", PAGE_COUNTER, 0, TCOB_KW_STD},
> {"PARAGRAPH", PARAGRAPH, 0, TCOB_KW_STD85},
> {"PERFORM", PERFORM, 0, TCOB_KW_STD},
> {"PF", PF, 0, TCOB_KW_STD},
>
>
> veja programa abaixo:
> identification division.
> program-id. paragraph01.
> author. Carlucio Lopes.
> environment division.
> configuration section.
> special-names.
> decimal-point is comma.
> data division.
> working-storage section.
> 77 wsn-parag pic 9(01).
> 88 wsc-parag-ok value 1 2 3.
> procedure division.
> move 1 to wsn-parag
> perform until wsn-parag = zero
> evaluate wsn-parag
> when 01 perform 000-parag
> when 02 perform 010-parag
> when 03 perform 020-parag
> when other move zero to wsn-parag
> end-evaluate
> end-perform
> stop run.
> 000-parag.
> display "000-parag " at 0910
> accept wsn-parag at 1010
> if not wsc-parag-ok
> display "Sai do programa" at 1110 stop " "
> exit paragraph
> end-if
> display "000-parag sai " at 1210.
> 010-parag.
> display "010-parag " at 0910
> accept wsn-parag at 1010
> if not wsc-parag-ok
> display "Sai do programa" at 1110 stop " "
> exit paragraph
> end-if
> display "010-parag sai " at 1210.
> 020-parag.
> display "020-parag " at 0910
> accept wsn-parag at 1010
> if not wsc-parag-ok
> display "Sai do programa" at 1110 stop " "
> exit paragraph
> end-if
> display "020-parag sai " at 1210.
>
>
> carlucio@carlinux:~$ htcobol -x -F -P paragraph01.cob
> paragraph01.cob: 28: error: syntax error, on or before 'paragraph'
> paragraph01.cob: 28: error: unknown or wrong statement, on or before
> 'paragraph'
> paragraph01.cob: 28: error: unknown or wrong statement, on or before
> 'paragraph'
> paragraph01.cob: 29: error: unknown or wrong statement, on or before
> 'end-if'
> paragraph01.cob: 35: error: syntax error, on or before 'paragraph'
> paragraph01.cob: 35: error: unknown or wrong statement, on or before
> 'paragraph'
> paragraph01.cob: 35: error: unknown or wrong statement, on or before
> 'paragraph'
> paragraph01.cob: 36: error: unknown or wrong statement, on or before
> 'end-if'
> paragraph01.cob: 42: error: syntax error, on or before 'paragraph'
> paragraph01.cob: 42: error: unknown or wrong statement, on or before
> 'paragraph'
> paragraph01.cob: 42: error: unknown or wrong statement, on or before
> 'paragraph'
> paragraph01.cob: 43: error: unknown or wrong statement, on or before
> 'end-if'
> carlucio@carlinux:~$
>
> com a alteracao:
> carlucio@carlinux:~$ htcobol -x -F -P paragraph01.cob
>
> compilou ok.
>
>
|
|
From: Carlucio L. <car...@te...> - 2009-02-27 12:02:36
|
Comando : EXIT PARAGRAPH
Para adquar o padrao STD85 MF solicito a sequinte alteracao:
arquivo htcobol.y
de:
%token ORGANIZATION OTHER OUTPUT OVERFLOW_TOK
%token PADDING PAGE PAGE_COUNTER PERFORM PF PH PICTURE PLUS POINTER POSITION
%token POSITIVE PREVIOUS PROCEDURE PROCEED PROGRAM PROGRAM_ID
...
..
/* EXIT statement */
exit_statement:
EXIT { gen_exit(0); }
| EXIT PROGRAM { gen_exit(1); }
;
para:
%token ORGANIZATION OTHER OUTPUT OVERFLOW_TOK
%token PADDING PAGE PAGE_COUNTER PARAGRAPH PERFORM PF PH PICTURE PLUS POINTER POSITION
%token POSITIVE PREVIOUS PROCEDURE PROCEED PROGRAM PROGRAM_ID
...
...
/* EXIT statement */
exit_statement:
EXIT { gen_exit(0); }
| EXIT PARAGRAPH { gen_exit(0); }
| EXIT PROGRAM { gen_exit(1); }
;
arquivo reswords.c :
de:
{"PAGE-COUNTER", PAGE_COUNTER, 0, TCOB_KW_STD},
{"PERFORM", PERFORM, 0, TCOB_KW_STD},
{"PF", PF, 0, TCOB_KW_STD},
para:
{"PAGE-COUNTER", PAGE_COUNTER, 0, TCOB_KW_STD},
{"PARAGRAPH", PARAGRAPH, 0, TCOB_KW_STD85},
{"PERFORM", PERFORM, 0, TCOB_KW_STD},
{"PF", PF, 0, TCOB_KW_STD},
veja programa abaixo:
identification division.
program-id. paragraph01.
author. Carlucio Lopes.
environment division.
configuration section.
special-names.
decimal-point is comma.
data division.
working-storage section.
77 wsn-parag pic 9(01).
88 wsc-parag-ok value 1 2 3.
procedure division.
move 1 to wsn-parag
perform until wsn-parag = zero
evaluate wsn-parag
when 01 perform 000-parag
when 02 perform 010-parag
when 03 perform 020-parag
when other move zero to wsn-parag
end-evaluate
end-perform
stop run.
000-parag.
display "000-parag " at 0910
accept wsn-parag at 1010
if not wsc-parag-ok
display "Sai do programa" at 1110 stop " "
exit paragraph
end-if
display "000-parag sai " at 1210.
010-parag.
display "010-parag " at 0910
accept wsn-parag at 1010
if not wsc-parag-ok
display "Sai do programa" at 1110 stop " "
exit paragraph
end-if
display "010-parag sai " at 1210.
020-parag.
display "020-parag " at 0910
accept wsn-parag at 1010
if not wsc-parag-ok
display "Sai do programa" at 1110 stop " "
exit paragraph
end-if
display "020-parag sai " at 1210.
carlucio@carlinux:~$ htcobol -x -F -P paragraph01.cob
paragraph01.cob: 28: error: syntax error, on or before 'paragraph'
paragraph01.cob: 28: error: unknown or wrong statement, on or before
'paragraph'
paragraph01.cob: 28: error: unknown or wrong statement, on or before
'paragraph'
paragraph01.cob: 29: error: unknown or wrong statement, on or before
'end-if'
paragraph01.cob: 35: error: syntax error, on or before 'paragraph'
paragraph01.cob: 35: error: unknown or wrong statement, on or before
'paragraph'
paragraph01.cob: 35: error: unknown or wrong statement, on or before
'paragraph'
paragraph01.cob: 36: error: unknown or wrong statement, on or before
'end-if'
paragraph01.cob: 42: error: syntax error, on or before 'paragraph'
paragraph01.cob: 42: error: unknown or wrong statement, on or before
'paragraph'
paragraph01.cob: 42: error: unknown or wrong statement, on or before
'paragraph'
paragraph01.cob: 43: error: unknown or wrong statement, on or before
'end-if'
carlucio@carlinux:~$
com a alteracao:
carlucio@carlinux:~$ htcobol -x -F -P paragraph01.cob
compilou ok.
--
Carlucio Lopes-Cobolito 62-8415-8939
Tinycobol/Debian Gnu-Linux/Postgresql
Novo Link PIRATARIA ENTENDA ->> http://carlinux.no-ip.info:81
|
|
From: Fred M. <fr...@mo...> - 2009-01-14 17:39:56
|
On Wednesday 14 January 2009 12:57, David Essex wrote:
> deu439 wrote:
> > Thanks, but I _didnt_ mean structures.
> >
> > Typedef; can be used for define new data type/structures.
> > So I can declare new variable/struct with defined aligment.
> >
> > Like this:
> >
> > //define data type "NAME"
> > typedef struct{
> > int a;
> > int b;
> > }NAME;
> >
> > main(){
> > //declare struct
> > //with "NAME" aligment
> > NAME declared_struct;
> > }
> >
> > Sorry whether it's too intuitive.
>
> AFAIK, COBOL (85 standard) does not differentiate between a
> declaration and definition (memory allocation). Meaning it does both
> in one step.
I don't understand the original question of OP, but I would like to add
to your statement above.
In a WORKING-STORAGE SECTION, declarations allocate memory and declare a
memory layout.
In a LINKAGE SECTION, declarations don't allocate memory but just
declare a memory layout. The memory is in general allocated in the
calling program in the WORKING-STORAGE SECTION.
Example :
PROGRAM-ID. A. <--- Main program.
...
WORKING-STORAGE SECTION. <--- allocation and layout.
01 AREA-A-1.
03 FIELD-A-1-A PICTURE X(7).
03 FIELD-A-1-B PICTURE X(3).
01 AREA-A-2.
03 FIELD-A-2-A PICTURE X(7).
03 FIELD-A-2-B PICTURE X(3).
01 AREA-A-3.
03 FIELD-A-3-A PICTURE X(7).
03 FIELD-A-3-B PICTURE X(3).
PROCEDURE DIVISION.
START SECTION.
P00.
CALL "B"
USING AREA-A-1
AREA-A-3.
EOS.
STOP RUN.
PROGRAM-ID. B. <--- Subroutine.
...
LINKAGE SECTION. <--- Only layout per 01 level.
01 AREA-B-1.
03 FIELD-B-1-A PICTURE X(7).
03 FIELD-B-1-B PICTURE X(3).
01 AREA-B-2.
03 FIELD-B-2-A PICTURE X(7).
03 FIELD-B-2-B PICTURE X(3).
PROCEDURE DIVISION USING AREA-B-1
AREA-B-2.
START SECTION.
P00.
....
EOS.
EXIT PROGRAM.
PLease notice that the subroutine B does not know if the arguments
AREA-B-1 and AREA-B-2 are located in adjacent area's or not. The main
program A knows they're NOT.
Often such structures are put in copy members in order to avoid
differences in declarations. But that results in another problem :
VALUE clauses are (were ?) not allowed in the linkage section.
--
Fred Mobach - fr...@mo... - pos...@mo...
website : http://fred.mobach.nl
.... In God we trust ....
.. The rest we monitor ..
|
|
From: David E. <de...@us...> - 2009-01-14 13:36:40
|
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). |
|
From: David E. <de...@us...> - 2009-01-14 12:53:51
|
deu439 wrote:
> Thanks, but I _didnt_ mean structures.
>
> Typedef; can be used for define new data type/structures.
> So I can declare new variable/struct with defined aligment.
>
> Like this:
>
> //define data type "NAME"
> typedef struct{
> int a;
> int b;
> }NAME;
>
> main(){
> //declare struct
> //with "NAME" aligment
> NAME declared_struct;
> }
>
> Sorry whether it's too intuitive.
AFAIK, COBOL (85 standard) does not differentiate between a declaration
and definition (memory allocation). Meaning it does both in one step.
However you can use qualification to achieve a similar effect.
Example:
...
01 NAME-A.
05 INT-A PIC S9(8).
05 INT-B PIC S9(8).
01 NAME-B.
05 INT-A PIC S9(8).
05 INT-B PIC S9(8).
...
MOVE INT-B OF NAME-A TO INT-A OF NAME-B.
> I found documentation of LINKAGE section in IBM web.
> Well I can define the data structure in LINKAGE section and next rewrite
> address of this structure to any other address, but it's too
> intricately.
> First I must acquire lenght of structure, allocate memory, until I can
> rewrite the address.
>
> Any other ideas, how can I do it in tiny cobol?
I don't understand what you are trying to accomplish.
In any case TC does support the following.
Pointers to a limited extent.
Example:
...
01 NAME-P POINTER.
...
SET idetifier-1 TO ADDRESS OF idetifier-2.
Length of identifiers.
Example:
...
01 INT-A PIC S9(4).
...
MOVE LENGTH OF idetifier-1 TO idetifier-2
Dynamic memory allocation is not supported in TC (COBOL 85 standard).
I think it was introduced in the COBOL 2002 standard.
Hope this helps.
HINT:
You can find some examples on how to mix COBOL/C/COBOL programs in the
'test.code' directories of the source code.
|
|
From: deu439 <de...@az...> - 2009-01-13 19:43:43
|
David Essex wrote:
> Assuming you mean C structures, '01' levels can be consided to provide
> equivalent functionality (with the C 'pragma pack(1)' directive).
Thanks, but I _didnt_ mean structures.
Typedef; can be used for define new data type/structures.
So I can declare new variable/struct with defined aligment.
Like this:
#################
//define data type "NAME"
typedef struct{
int a;
int b;
}NAME;
main(){
//declare struct
//with "NAME" aligment
NAME declared_struct;
}
#################
Sorry whether it's too intuitive.
I found documentation of LINKAGE section in IBM web.
Well I can define the data structure in LINKAGE section and next rewrite
address of this structure to any other address, but it's too
intricately.
First I must acquire lenght of structure, allocate memory, until I can
rewrite the address.
Any other ideas, how can I do it in tiny cobol?
-------------------
de...@in...
Czech Republic
|
|
From: David E. <de...@us...> - 2009-01-13 09:01:58
|
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. |
|
From: deu439 <de...@az...> - 2009-01-12 16:36:13
|
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 |
24 messages has been excluded from this view by a project administrator.
