tiny-cobol-users

Re: [Tiny-cobol-users] tk support

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

Jon Shorie wrote:

> Has anyone looked at supporting a .tk interface to tiny cobol?
> 
> We use fujitsu cobol here for some internal apps that run on desktop pc's.  We 
> are looking at options to migrate them to something that is more cross 
> platform than being locked in to win32.
> 
> As they have a significant amount of business logic in the code, it would be 
> very expensive to migrate to another language than cobol for these.
> 
> We have looked at the .tk toolkit because it would standardize our other 
> internal apps that are based in languages such as perl, python, pascal, etc.

Yes you can use many GUI front ends with TC.
The 'gui*' examples found in the 'test.code' directories (included with
the source code), include working examples using TCL/TK, Wind*ws API and
GTK.

Basically, the COBOL (sub)programs can be considered as just as another
C type function call of type 'int program(...)'.

Have you considered using a 'client/server' model. The data and
'business logic' reside on a server and is displayed locally.

This approach can yield good COBOL code reuse, without major source code
modifications.

The easiest of these methods, would be to use a web interface to display
and update information.

Anyway, hope this helps.

Re: [Tiny-cobol-users] [Fwd: Re: Sample for testing "backwards" perform thru (fwd)]

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

Bill Gunshannon wrote:

> I will pass this info back to the comp.lang.cobol community.
Well, OK.
But as I have no plans to create a new TC release anytime in the near 
future, they will have to download (and build) this version from SF CVS.

> I'll bet MicroF*cus doesn't get fixes out this fast. :-)
Probably not, but the do have the money to buy most of their competitors.

Cheers.

Re: [Tiny-cobol-users] [Fwd: Re: Sample for testing "backwards" perform thru (fwd)]

[Bill G. <bi...@cs...>]

I will pass this info back to the comp.lang.cobol community.
I'll bet MicroFocus doesn't get fixes out this fast. :-)

bill

> David Essex wrote:
>> Bill Gunshannon wrote:
>> ...
>>> Not sure if you (or anyone over here) are in a position to look
>>> at this or even care, but I gleaned this from comp.lang.cobol.
>>
>> Thanks for the information Bill.
>>
>> Unfortunately, there is no easy fix for this problem, as it would
>> require some sort of a syntax tree. And TC does not use a syntax tree.
>>
>> Actually, a lack of a syntax tree creates all sort of problems.
>>
>> Frankly, I don't have the time, or inclination, to FIX this problem.
>
> I have found a quick and easy fix which seams to work without any
> apparent problems.
>
> I have uploaded this fix to SF CVS, version 0.64.3.
>
> Sample program:
> Program-ID. PERFTHRU.
> Procedure Division.
> Mainline.
>   Display "In Mainline"
>   Perform Para3 Thru Para1
>   Display "After Perform"
>   Stop Run.
> Para1.
>   Display "In para1".
> Para2.
>   Display "In Para2".
> Para3.
>   Display "In para3".
> Para4.
>   Display "In para4".
> Alternate-End.
>   Stop Run.
>
> TC version 0.64:
> In Mainline
> In para3
> After Perform
>
> TC version 0.64.3:
> In Mainline
> In para3
> In para4
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Tin...@li...
> https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users
>


-- 
Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves
bi...@cs...     |  and a sheep voting on what's for dinner.
University of Scranton   |
Scranton, Pennsylvania   |         #include <std.disclaimer.h>

Re: [Tiny-cobol-users] [Fwd: Re: Sample for testing "backwards" perform thru (fwd)]

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

David Essex wrote:
> Bill Gunshannon wrote:
> ... 
>> Not sure if you (or anyone over here) are in a position to look
>> at this or even care, but I gleaned this from comp.lang.cobol.
> 
> Thanks for the information Bill.
> 
> Unfortunately, there is no easy fix for this problem, as it would
> require some sort of a syntax tree. And TC does not use a syntax tree.
> 
> Actually, a lack of a syntax tree creates all sort of problems.
> 
> Frankly, I don't have the time, or inclination, to FIX this problem.

I have found a quick and easy fix which seams to work without any 
apparent problems.

I have uploaded this fix to SF CVS, version 0.64.3.

Sample program:
Program-ID. PERFTHRU.
Procedure Division.
Mainline.
  Display "In Mainline"
  Perform Para3 Thru Para1
  Display "After Perform"
  Stop Run.
Para1.
  Display "In para1".
Para2.
  Display "In Para2".
Para3.
  Display "In para3".
Para4.
  Display "In para4".
Alternate-End.
  Stop Run.

TC version 0.64:
In Mainline
In para3
After Perform

TC version 0.64.3:
In Mainline
In para3
In para4

Re: [Tiny-cobol-users] tk support

[John C. <jo...@we...>]

On Wednesday 19 November 2008 08:16:02 am Jon Shorie wrote:
> Has anyone looked at supporting a .tk interface to tiny cobol?
>
> We use fujitsu cobol here for some internal apps that run on
> desktop pc's.  We are looking at options to migrate them to
> something that is more cross platform than being locked in to
> win32.
>
> As they have a significant amount of business logic in the code, it
> would be very expensive to migrate to another language than cobol
> for these.
>
> We have looked at the .tk toolkit because it would standardize our
> other internal apps that are based in languages such as perl,
> python, pascal, etc.
>
> Thank you
>
> Jon Shorie
> Systems Adminstrator
> Medina County Sanitary Engineers
> 330-764-8332
>

Look in subfolders test.code/tgui01 and test.code/tgui02 to see 
Rildo's approach. 
-- 
John Culleton
Resources for every author and publisher:
http://wexfordpress.com/tex/shortlist.pdf
http://wexfordpress.com/tex/packagers.pdf
http://www.creativemindspress.com/newbiefaq.htm
http://www.gropenassoc.com/TopLevelPages/reference%20desk.htm

[Tiny-cobol-users] tk support

[Jon S. <js...@me...>]

Has anyone looked at supporting a .tk interface to tiny cobol?

We use fujitsu cobol here for some internal apps that run on desktop pc's.  We 
are looking at options to migrate them to something that is more cross 
platform than being locked in to win32.

As they have a significant amount of business logic in the code, it would be 
very expensive to migrate to another language than cobol for these.

We have looked at the .tk toolkit because it would standardize our other 
internal apps that are based in languages such as perl, python, pascal, etc.

Thank you

Jon Shorie
Systems Adminstrator
Medina County Sanitary Engineers
330-764-8332

Re: [Tiny-cobol-users] [Fwd: Re: Sample for testing "backwards" perform thru (fwd)]

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

Bill Gunshannon wrote:
...
> Not sure if you (or anyone over here) are in a position to look
> at this or even care, but I gleaned this from comp.lang.cobol.

Thanks for the information Bill.

Unfortunately, there is no easy fix for this problem, as it would
require some sort of a syntax tree. And TC does not use a syntax tree.

Actually, a lack of a syntax tree creates all sort of problems.

Frankly, I don't have the time, or inclination, to FIX this problem.

Cheers

[Tiny-cobol-users] [Fwd: Re: Sample for testing "backwards" perform thru (fwd)]

[Bill G. <bi...@cs...>]

David,

  Not sure if you (or anyone over here) are in a position to look
at this or even care, but I gleaned this from comp.lang.cobol.

bill

---------------------------- Original Message ----------------------------
Subject: Re: Sample for testing "backwards" perform thru (fwd)
From:    "Bill Gunshannon" <bil...@cs...>
Date:    Fri, November 14, 2008 1:47 pm
To:      bi...@cs...
--------------------------------------------------------------------------

Path: uni-berlin.de!individual.net!not-for-mail
From: bil...@cs... (Bill Gunshannon)
Newsgroups: comp.lang.cobol
Subject: Re: Sample for testing "backwards" perform thru
Date: 14 Nov 2008 18:40:51 GMT
Organization: Computing Sciences Dept., University of Scranton
Lines: 126
Message-ID: <6o5...@mi...>
References: <PB1Tk.165855$f64...@fe...>
    <6o5...@mi...>
    <b6a...@s1...>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: individual.net DDY0WBw1Wiandv4LBr0XBAKkBAPsTnkpfnb9HR0VYvshgOU3Y/
Cancel-Lock: sha1:F1AXkS1zz2ggOU28s0I5BlG/j7Y=
X-Newsreader: knews 1.0b.1
Xref: uni-berlin.de comp.lang.cobol:177590

In article
<b6a...@s1...>,
	Richard <ri...@Az...> writes:
> On Nov 15, 3:26 am, billg...@cs.uofs.edu (Bill Gunshannon) wrote:
>> In article <PB1Tk.165855$f64.161...@fe05.news.easynews.com>,
>>         "William M. Klein" <wmkl...@nospam.netcom.com> writes:
>>
>> > There were some comments about testing support for and behavior of
>> >   Perform procedure-name-1 thru procedure-name-2
>> > where Procedure-name-2 actually appears BEFORE procedure-name-1 in
the source
>> > code.
>>
>> > The following is a sample program to test whether "your" compiler
supports this
>> > (compiles it) and what happens.  I *think* (but won't swear to it)
that all
>> > (most?) compilers will compile this and display "In para4" and then
terminate.
>>
>> Boy are you in for a surprise!!
>>
>>
>>
>> >  (I don't think that such compiler options as "perform-type" (MF) or
OPT (IBM)
>> > will impact this, but I won't swear to that).
>>
>> >   * * *
>>
>> >        Identification Division.
>> >         Program-ID. PERFTHRU.
>> >        Procedure Division.
>> >         Mainline.
>> >            Display "In Mainline"
>> >            Perform Para3 Thru Para1
>> >            Display "After Perform"
>> >            Stop Run
>> >             .
>> >        Para1.
>> >            Display "In para1"
>> >              .
>> >        Para2.
>> >            Display "In Para2"
>> >               .
>> >        Para3.
>> >            Display "In para3"
>> >              .
>> >        Para4.
>> >            Display "In para4"
>> >              .
>> >        Alternate-End.
>> >            Stop Run
>> >              .
>>
>> I tried it with both OpenCOBOL and TinyCOBOL.  Both compiled the code
without
>> comment or complaint.  Here are the results:
>>
>> OpenCOBOL:
>>
>> In Mainline
>> In para3
>> In para4
>>
>> TinyCOBOL:
>>
>> In Mainline
>> In para3
>> After Perform
>>
>> But then, isn't that what "Undefined" means?  :-)
> TinyCobol is very broken then.

Not sure I would agree with that.  Undefined is undefined.  Seems that
grants rather a wide latitude for interpretation.

>                                  It has made an arbitrary decision to
> not execute the code in Para4. For example it may have been that in
> Para4 there was a GO TO Para1 that completed the PERFORM.

Ah!!  Now I see what you mean.  Interesting point and, I would have to agree.
They probably don't care, but I will likely forward this on to them.

> What _is_ clearly defined is that with a PERFORM THRU the path should
> 'drop through' until the end point is reached (granted it never could
> be in this test).
> Cobol also states what happens when a STOP RUN is reached (in
> Alternate end) or if the path falls off the end of the code (ie if the
> Alternate-end paragraph was removed).
> The other compilers get it right.

Yeah, in light of the standard.  But I think the compiler should have done
like the Fuji-Siemens and at least told the programmer his code was crap
and give him a chance to fix it.  :-)  I am also glad (even though I really
don't get to do COBOL for a living anymore) that I never worked ina shop
that would have allowed something like this anywhere near a compiler.

>> I can't make any promises but it would be fun to try it with things like
>> some of my old Ryan-McFarland compilers and maybe the one from OpenVMS
>> or one of the old PDP-11 COBOL's. Could be interesting to see just how
>> many different ways there are to nterpret the concept.
> There is only one way to correctly interpret what happens with the
> code. There is nothing to direct the path of execution back to Para1
> before the STOP RUN or 'falling off the end'. Neither of which will
> cause an error message.
> Would you hope to find a compiler that did it differently ?

As I said, I would hope to never see code like this and I think, given the
availability of resources today, that all compilers should point out the
folly of this kind of code.

> Do you think that TinyCobol is better ?

Didn't say anything was better or worse.  I just ran it thru the two
compilers I have close at hand and posted the results.  When I have
time I will run it thru other (usually much older) compilers just to
see what happens.

> I certainly don't want arbitrary decisions made that make programs do
> something different from what the source code indicates will happen.

And, of course, the real solution to this is don't write arbitrary code.
Write you programs to do what you want and only what you want and you
will never have to worry about the compiler making arbitrary decisions.

bill

-- 
Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves
bil...@cs... |  and a sheep voting on what's for dinner.
University of Scranton   |
Scranton, Pennsylvania   |         #include <std.disclaimer.h>


-- 
Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves
bi...@cs...     |  and a sheep voting on what's for dinner.
University of Scranton   |
Scranton, Pennsylvania   |         #include <std.disclaimer.h>

[Tiny-cobol-users] TC release version 0.64

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

The TinyCOBOL compiler version 0.64 is available for download at the TC
home page (1).

Lots of bug fixes and improvements.
File IO run-time has been re-written and now supports variable length 
sequential, relative and indexed files.
On the negative side, FILE/RECORD locks are NOT supported. The BDB 185 
API does not support locks. And as usual wind*ws does not support UN*X 
type locks (not that I could find ...).

Important:
The indexed file format has changed and is incompatible with previous TC 
versions.
The new format uses two files. A BDB file which contains all indexes, 
and a sequential file which contains the data.
Do NOT attempt to read/write old indexed files using TC 0.64.
It is recommended that all indexed files be re-build, from a sequential 
file, using TC 0.64.

Please report any bugs and/or problems to the TC mailing list.


1) TinyCOBOL Home Page
http://tiny-cobol.sourceforge.net/
http://sf.net/project/showfiles.php?group_id=383

Re: [Tiny-cobol-users] Bug fix for numeric edited types MOVEs

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

m_maass wrote:
> Thank for your hints. Library check - OK.
> The problem come unfortunately from gcc.
> The compiled executable m1 work with gcc 3.4.6 (Slackware pasture) but 
> with gcc 4.2.3 (Slackware 12.1) I become segmentation fault.

Thanks for the feed-back.

It seems that GCC 3.x and 4.x are quite different, internally.

Unfortunately, I don't have GCC 4.x installed and have no way to
identify and fix this problem.
So I will release TC 0.64 as is, and hope for the best.

Re: [Tiny-cobol-users] Bug fix for numeric edited types MOVEs

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

m_maass wrote:
> sorry, the fix do not work on my configuration (Slackware 12.1) 
> with TC 0.63.145.
> I become Segmentation fault.
> Please look at the attached typescript.

I'm unable to duplicate this problem on my system.
Note that TC will work on 32-bit (x86-32) systems only.

#htcobol -V
TinyCOBOL pre-alpha 0.63.145 ...

#m1
Please enter 123.45
123.45
123.45 should be 123.45

OR with some integer data

#m1
Please enter 123.45
12345
345.00 should be 123.45
Note that '345.00' is correct.

Other than some issues with GCC (I hope not), the only other remote
possibility I can think of is a TC compiler run-time mis-match.
Meaning that the linker is using the wrong library.

You can use the LDD and LS commands to check ...
#ldd m1
libhtcobol.so.0 => /usr/lib/libhtcobol.so.0 ...
...

#ls -l /usr/lib/libhtcob*
#ls -l /usr/lib/local/libhtcob*

If this is the case, un-install TC (make uninstall), check and remove
any other TC libs.
Then re-install (make install) and update (ldconfig -v).

Anyway, I hope this helps.

[Tiny-cobol-users] Bug fix for numeric edited types MOVEs

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

David Essex wrote:
...
> Yes, there is a bug with the MOVE verb of numeric edited types.

OK, fixed.
Fix is available with TC 0.63.145 (or later).

Hopefully this will be the last fix before TC 0.64 is released.

Re: [Tiny-cobol-users] bug in 0.63.139

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

m_maass wrote:

> please look at the attached example. 
> Input number is not equal to  output number.

Yes, there is a bug with the MOVE verb of numeric edited types.

01 E-ZAHL PIC ZZZ.99.
01 ZAHL   PIC ZZZ.99.
...
* This move works as expected
MOVE 123.45 TO E-ZAHL
* This move does NOT work properly
MOVE E-ZAHL TO ZAHL.

I will try to fix this bug before TC version 0.64 is released.

As a temporary fix, avoid moves between edited types.

Example:
...
05 E-ZAHL PIC 999V99.
05 ZAHL   PIC ZZZ.99.
...
ACCEPT E-ZAHL.
MOVE   E-ZAHL TO ZAHL.

Hope this helps.

Re: [Tiny-cobol-users] Tiny-cobol-users Digest, Vol 25, Issue 1

[Adam H. <aha...@gm...>]

remove

On Sat, Oct 11, 2008 at 1:03 PM, <
tin...@li...> wrote:

> Send Tiny-cobol-users mailing list submissions to
>        tin...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users
> or, via email, send a message with subject or body 'help' to
>        tin...@li...
>
> You can reach the person managing the list at
>        tin...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tiny-cobol-users digest..."
>
>
> Today's Topics:
>
>   1.  whereis htcobol?? (irado)
>   2. Re: whereis htcobol?? (David Essex)
>   3. htcobol can not compile, hang-up (m_maass)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 26 Sep 2008 10:40:48 -0700 (PDT)
> From: irado <ir...@sa...>
> Subject: [Tiny-cobol-users]  whereis htcobol??
> To: tin...@li...
> Message-ID: <196...@ta...>
> Content-Type: text/plain; charset=us-ascii
>
>
> configured/compiled/install WITHOUT errors or warnings. htcobrun is there
> but
> htcobol disappear (never made, at all).
>
> version 0.62 and 0.63 - yes, I am trying a lot, since long.
>
> Question: HOW can I have the compiler done?
>
> system: Slackware Linux 12.1
>
>
> --
> View this message in context:
> http://www.nabble.com/whereis-htcobol---tp19693229p19693229.html
> Sent from the tiny-cobol-users mailing list archive at Nabble.com.
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 05 Oct 2008 15:03:23 -0400
> From: David Essex <de...@us...>
> Subject: Re: [Tiny-cobol-users] whereis htcobol??
> To: tiny-cobol-users <tin...@li...>
> Message-ID: <48E...@us...>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> irado wrote:
>
> > configured/compiled/install WITHOUT errors or warnings. htcobrun
> > is there but htcobol disappear (never made, at all).
> >
> > version 0.62 and 0.63 - yes, I am trying a lot, since long.
> >
> > Question: HOW can I have the compiler done?
>
> The default configure build prefix is '/usr/local'.
> On some newer system these paths (/usr/local/bin and /usr/local/lib) are
> not setup by default.
>
> First, verify that TC was installed.
> #ls -l "/usr/local/bin/htcob*"
> #ls -l "/usr/local/lib/libhtcob*"
>
> If TC was installed, you can do one of the following.
>
> Add '/usr/local/bin' to your PATH, and '/usr/local/lib' to the dynamic
> linker (/sbin/ldconfig) library paths.
>
> Or remove and re-build TC with the '/usr' confugure prefix.
> #./configure --prefix=/usr
> #make
> #make install
> Run the dynamic linker configure (see man ldconfig), to update the
> library cache.
>
> > system: Slackware Linux 12.1
>
> BTW, I have added a Slackware build script to CVS
> ('info/slackware/SlackBuild').
> Should work on 'Slackware 12.1', with minor modifications, using the TC
> 0.63 sources.
>
> Or you can wait for TC 0.64, which should be out by the end of October,
> I hope.
>
> Hope this helps.
>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 11 Oct 2008 20:03:27 +0200
> From: m_maass <m_...@we...>
> Subject: [Tiny-cobol-users] htcobol can not compile, hang-up
> To: tin...@li...
> Message-ID: <48F...@we...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Howdy,
>
> i have some problem wit compiling my third Cobol source, htcobol hang-up.
> The source is from one book from 1988.  (See attachment.)
>
> My system:
> system: Slackware 12.1 Linux darkstar 2.6.25 #1 Tue May 6 19:39:30 CEST
> 2008 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux
>
> Version:
> htcobol -V
> TinyCOBOL pre-alpha 0.63.139 (linux-gnu 2008/10/11)
> Copyright (C) 1991, 1993, 1999-2008 Rildo Pragana
> created today, from cvs.
>
> typescript from build htcobol is also attached.
>
> My htcobol hang-up after this command:
>
> htcobol -v demo1-zinsen.cob
> Pre-processing 'demo1-zinsen.cob' into 'demo1-zinsen.i'
> Generating assembler output file 'demo1-zinsen.s' from input
> 'demo1-zinsen.i'
>
> Is the problem only on my system or is it a generic problem?
>
> Thank, and sorry for my alien English
>
> Mike
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: typescript
> Type: application/octet-stream
> Size: 23171 bytes
> Desc: not available
> -------------- next part --------------
> An embedded and charset-unspecified text was scrubbed...
> Name: demo1-zinsen.cob
>
> ------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>
> ------------------------------
>
> _______________________________________________
> Tiny-cobol-users mailing list
> Tin...@li...
> https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users
>
>
> End of Tiny-cobol-users Digest, Vol 25, Issue 1
> ***********************************************
>

[Tiny-cobol-users] bug in 0.63.139

[m_maass <m_...@we...>]

Howdy,

please look at the attached example. 
Input number is not equal to  output number.

Thank You

Mike

Re: [Tiny-cobol-users] htcobol can not compile, hang-up

[m_maass <m_...@we...>]

David,

your suggestion to work with Berkely yacc 193 has resolved my problem.

Thank.

Mike

Re: [Tiny-cobol-users] htcobol can not compile, hang-up

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

m_amass wrote:
...
> i have some problem wit compiling my third Cobol source, htcobol hang-up.
> The source is from one book from 1988.  (See attachment.)
> ... 
> Is the problem only on my system or is it a generic problem?

This a bug related to the TC COBOL grammar and Bison.
It occurs once in a while with no apparent reason or warning.

The syntax in question is 'CONSOLE IS CRT' in the 'SPECIAL-NAMES'
clause. TC does NOT currently support this syntax.
TC should just trap this as an error and print the error message.

When the TC COBOL grammar is compiled with YACC193 [1] (Berkeley's YACC
version 1.9.3), the same syntax will print an error message and exit
normally.
I have no idea how to fix this bug, other than suggesting using YACC193.

Just change the code as follows and it should compile and run.
SPECIAL-NAMES.
  DECIMAL-POINT IS COMMA
* CONSOLE IS CRT
  .
*INPUT-OUTPUT SECTION.
*FILE-CONTROL.
...
VERARBEITUNG SECTION.
VER-1000.
*DISPLAY SPACE UPON CRT.
...

BTW, if you using the fixed COBOL source format, to avoid problems add
the '-F' or '--fixed' option to the command line.

Hope this helps.

1) Berkeley's YACC version 1.9.3 (byacc) can be downloaded only from the
TC 'snapshot' web page.

[Tiny-cobol-users] htcobol can not compile, hang-up

[m_maass <m_...@we...>]

Howdy,

i have some problem wit compiling my third Cobol source, htcobol hang-up.
The source is from one book from 1988.  (See attachment.)

My system:
system: Slackware 12.1 Linux darkstar 2.6.25 #1 Tue May 6 19:39:30 CEST
2008 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux

Version:
htcobol -V
TinyCOBOL pre-alpha 0.63.139 (linux-gnu 2008/10/11)
Copyright (C) 1991, 1993, 1999-2008 Rildo Pragana
created today, from cvs.

typescript from build htcobol is also attached.

My htcobol hang-up after this command:

htcobol -v demo1-zinsen.cob
Pre-processing 'demo1-zinsen.cob' into 'demo1-zinsen.i'
Generating assembler output file 'demo1-zinsen.s' from input
'demo1-zinsen.i'

Is the problem only on my system or is it a generic problem?

Thank, and sorry for my alien English

Mike

Re: [Tiny-cobol-users] whereis htcobol??

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

irado wrote:

> configured/compiled/install WITHOUT errors or warnings. htcobrun 
> is there but htcobol disappear (never made, at all).
> 
> version 0.62 and 0.63 - yes, I am trying a lot, since long.
> 
> Question: HOW can I have the compiler done?

The default configure build prefix is '/usr/local'.
On some newer system these paths (/usr/local/bin and /usr/local/lib) are
not setup by default.

First, verify that TC was installed.
#ls -l "/usr/local/bin/htcob*"
#ls -l "/usr/local/lib/libhtcob*"

If TC was installed, you can do one of the following.

Add '/usr/local/bin' to your PATH, and '/usr/local/lib' to the dynamic
linker (/sbin/ldconfig) library paths.

Or remove and re-build TC with the '/usr' confugure prefix.
#./configure --prefix=/usr
#make
#make install
Run the dynamic linker configure (see man ldconfig), to update the
library cache.

> system: Slackware Linux 12.1

BTW, I have added a Slackware build script to CVS
('info/slackware/SlackBuild').
Should work on 'Slackware 12.1', with minor modifications, using the TC
0.63 sources.

Or you can wait for TC 0.64, which should be out by the end of October,
I hope.

Hope this helps.

[Tiny-cobol-users] whereis htcobol??

[irado <ir...@sa...>]

configured/compiled/install WITHOUT errors or warnings. htcobrun is there but
htcobol disappear (never made, at all).

version 0.62 and 0.63 - yes, I am trying a lot, since long.

Question: HOW can I have the compiler done?

system: Slackware Linux 12.1


-- 
View this message in context: http://www.nabble.com/whereis-htcobol---tp19693229p19693229.html
Sent from the tiny-cobol-users mailing list archive at Nabble.com.

Re: [Tiny-cobol-users] Bug in tinycobol array display

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

V G K Dinavahi wrote:
>
> I would like to bring to your notice a small bug in tinycobol
> array display. I here with enclosing a small code.
> In this code I used occurs to accept input from user and display
> the same immediately. But it is displaying the first name only.
> But it storing w-name 10 times in occurs if we used to display
> w-name(1), w-name(2)...w-name(10) like that it is showing correctly.
> But putting in loop and displaying like display w-name(i) until 10
> times it is not showing properly.
> I Checked the same code with OpenCobol and Microf*cus cobol also
> in those compilers it is showing correctly.
>
> If possible fix the same before release the new version.

I fixed this bug, me thinks.

This fix, among many others, will be included in TC version 0.64 and is
available on SF CVS version 0.63.121 or greater.

Hope this helps.

Re: [Tiny-cobol-users] Bug in tinycobol array display

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

V G K Dinavahi wrote:

> I would like to bring to your notice a small bug in tinycobol array display.  
> I herewith enclosing a small code.  
> In this code I used occurs to accept input from user and display 
 > the same immediately.
> But it is displaying the first name only.
> But it storing w-name 10 times in occurs if we used to display
 > w-name(1),w-name(2)...w-name(10) like that it is showing correctly.
> But putting in loop and displaying like display w-name(i) until 10 times 
 > it is not showing properly.
> I Checked the same code with OpenCobol and Microfocus cobol also in those 
 > compilers it is showing correctly.
> 
> If possible fix the same before release the new version.

Yes, this is a bug which was present in version 0.63.

I will try to fix it for version 0.64.

In the meantime you can use a non-indexed identifier as a work around.
Basically you can use an non-indexed identifier to display/accept the 
data, and then move the data into the indexed identifier.

You can then display the input data using an indexed identifier, as in 
the enclosed a working example.

...
working-storage section.
  01 w-rec.
     05 w-name     pic x(10) occurs 10 times.
  01 w-name-1      pic x(10).
  01 i             pic 9(02).
  01 loc-i         pic 9(04).
  01 loc-name      pic 9(04).
  01 dummy         pic x(01).

procedure division.
A000.
  move 1 to i.
  move all '+' to w-rec.
  perform main-para
     until i > 4.
  move 1 to i.
  move 1101 to loc-i.
  move 1116 to loc-name.
  perform end-para
     until i > 5.
  accept dummy at 1627.
  stop run.

main-para.
  display i at 1001.
  accept w-name-1 at 1005.
  move w-name-1 to w-name(i).
  display w-name-1 at 1016.
  accept dummy at 1027.
  move '-------' to w-name-1.
  display w-name-1 at 1016.
  add 1 to i.

end-para.
  display i at loc-i.
  display w-name(i) at loc-name.
  add 100 to loc-i.
  add 100 to loc-name.
  add 1 to i.

Final display using TC 0.63.103:

04  4444444444 -------    4

01             1111111111
02             2222222222
03             3333333333
04             4444444444
05             ++++++++++


Hope this helps.

[Tiny-cobol-users] Bug in tinycobol array display

[<vgk...@in...>]

Hi All

I would like to bring to your notice a small bug in tinycobol array display.  
I herewith enclosing a small code.  In this code I used occurs to accept input from user and display the same immediately.  But it is displaying the first name only.  But it storing w-name 10 times in occurs if we used to display w-name(1),w-name(2)...w-name(10) like that it is showing correctly.  But putting in loop and displaying like display w-name(i) until 10 times it is not showing properly.  I Checked the same code with OpenCobol and Microfocus cobol also in those compilers it is showing correctly.  

If possible fix the same before release the new version.

Sorry for my poor english.

Thinking you,

V G K Dinavahi

[Tiny-cobol-users] Prepering TC 0.64

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

Hi All,

I would like to release the final version of TC (0.64), in the next 
couple of weeks. So I would like to fix any problems or bugs.

Anyone who would like to and try this (new and improved NO money back 
guarantee, as NOT seen on TV) pre-release version, just use enclosed 
simple CVS-bash download script (1).

Note that MinGW version should compile and run, but is not up to date 
and incomplete.

Please post any comments and suggestions to the TC mailing list.

Any help would be appreciated.

David Essex

1) SF CVS checkout script for TC (press enter at the password prompt)
#!/bin/bash -
#
cvsopt01='-d:pserver:ano...@ti...:/cvsroot/tiny-cobol'
#
p_anonymousCheckout ()
{
  cvs $1 login
  cvs -z3 $1 co -P development
}
#
p_anonymousCheckout "$cvsopt01"

Re: [Tiny-cobol-users] mistake make install compiler

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

Soporte Solint wrote:
...
 > Trying make compiler, display the next Messenger:
 > ...
 > gcc -I/usr/include -I/usr/local/include -I../lib -I../ -c scan.c
 >
 > scan.c:1061: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
 > before ‘YY_PROTO’
 > scan.l:744: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
 > before ‘YY_PROTO’
 > ...
 > And it doesn’t create the file “htcobol”, the way I can’t compile,
 > please can you help me to resolve this problem.

Asumming you are using TC version 0.63, then I think this is a macro
'define' problem with flex versions greater than 2.5.3.

This will cause the 'htcobol' build to fail to compile.

It is caused by the following macro 'define', as found in scan.l:61.

#define YY_DECL int yylex2 YY_PROTO((void))

The following code should fix the problem for all version (I hope) of flex.

#ifdef YY_USE_PROTOS
#define YY_DECL int yylex2 YY_PROTO((void))
#else
#define YY_PROTO(proto) (void)
#define YY_DECL int yylex2(void)
#endif

So just copy and change the file.
# cp -i scan.l scan.0.l
# nedit scan.l
... change and save the file
make

 > I am using a Linux suse 10.0.x whit a language in spanish.
 >
 > While I was executing (configure) it produce the next file:
 >
 > This file contains any messages produced by compilers while
 >
 > running configure, to aid debugging if configure makes a mistake.
 > ...
 > I didn’t have problems installing the rest of the opcions, thank you to
 > any help.

TC generates 32-bit GNU assembler code (IA32), and looking at the 
'configure'
trace it seams you are using GCC 4.x on a 64-bit system.

In theory this should not be a problem.

However TC 0.63 (configure, build and run) has never been tested with
either GCC 4.x or on a 64-bit system.

I plan to test TC 0.64 (if I ever get it finished) using GCC 4.x.
However, at the moment, I do not have access to a 64-bit system. So
there is no way I can test and resolve any 64-bit issues.

For version 0.63, the only thing I can suggest is to re-generate the
'configure' script. This may help, or create further problems.

# make cleandist
# mv -i configure configure.0
# autoconf
# configure ...
...

Hope this helps.