gnucobol-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [open-cobol-list] open-cobol-list Digest, Vol 10, Issue 4


From: Robert Keane
Subject: Re: [open-cobol-list] open-cobol-list Digest, Vol 10, Issue 4
Date: Wed, 11 Apr 2007 15:22:02 -0400
User-agent: Thunderbird 1.5.0.5 (X11/20060725)

address@hidden wrote:
Send open-cobol-list mailing list submissions to
	address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/open-cobol-list
or, via email, send a message with subject or body 'help' to
	address@hidden

You can reach the person managing the list at
	address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of open-cobol-list digest..."


Today's Topics:

   1. Re: Introducing myself...(line numbers) (John R. Culleton)


----------------------------------------------------------------------

Message: 1
Date: Tue, 10 Apr 2007 15:28:08 -0400
From: "John R. Culleton" <address@hidden>
Subject: Re: [open-cobol-list] Introducing myself...(line numbers)
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain;  charset="iso-8859-1"

On Tuesday 10 April 2007 12:49, Alain Lucari wrote:
  
John,

Nothing is "perfect" ... But O-C is the better you can have for
free or, even, with dollars.
In a old time I have used M-F and Acu and they are not PERFECT :
you must correct your program in order to use one or the other.
O-C try with his flavours to help anybody to compile program writed
with no_correction : this is too much for me, if you want to use a
compiler YOU must do what you do for use it.

About five years ago I try to use Tiny (thanks Rildo for his work)
but, sometimes some programs do'nt compile without any message
(because the same name in a copy and the working-storage-section,
most of the times MF and Acu accept that and take what ?)

In a first time, I have used O-C just for discover "where is the
problem" and after found, correct the mistake and compile with
tiny. After, I have worked a little with keisuke and explain where
are some problems for cobol program. Keisuke don't know Cobol but
is very good in C and I well know cobol and can explain where are
some problems.
At this time, I have about 660 programs totalizing 237 000 lines
running in production with O-C 0-23.19 because I have well tested,
with PostgreSQL with my own interface, on about 40 PCs.

Seriously, is somedody using NOW Accept/Dispalay at line/column ?
the worst thing I know.
If someone is interested I can send my "Eclair" product, really
better, free and the interface with pg also ...
BUT you must work a little : free or paying, nothing is without
a less of work ;-))

Be cool : now line/column is deprecated, use php or java, perhaps
with some money ... or most work.

Because my bad english (U.S) and the time for write with it,
I don't post too much, but yours asks are too out_of_date for me.
But, if you write french, you can post to me in it ... ^-(

Regards,

Alain Lucari (Eurlix)
    

I have forgotten all my French. Pardonnez moi je vous en prie.

If your "Eclair" will interface COBOL with a more suitable language I 
would be interested.  I already have an interface example from Rildo 
to put Tcl/TK and Cobol together. The difficult part is editing data 
as it is keyed in against a Cobol file. For example, if I am editing 
a customer order, but the customer number I enter is invalid, I want 
immediate notification before work proceeds further. DISPLAY/ACCEPT 
with positioning allows this interactive editing as work proceeds but 
there are obvious visual problems.  The difficulty lies not with 
COBOL but with the other language in use.

All suggestions gratefully accepted.  



  
Why not skip the Accept/Display method altogether and try using a browser as input. You can edit on the client side using _javascript_ or if you have to pass an input against a file for verification, do so on the serverside and report errors back to the browser.

Regards,

Robert Keane

reply via email to

[Prev in Thread] Current Thread [Next in Thread]