|
From: | Ralph |
Subject: | [Bug-GnuCOBOL] GnuCobol V3 RC1 |
Date: | Wed, 20 Mar 2019 16:05:40 -0400 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.2 |
I would kindly request a reply from either
Brian or Simon. Just to put this in perspective I recompiled all the source code for the animation effort with -fassign=ibm. What a disaster ! I have provided a simple program to illustrate the problem: FILEEPROB.COB There is an additional file that is just read for the test case EXMPFILE.COB it is just there for ease of looking at the test case. I don't think I am on board with your direction or your responsiveness. Please affirm that GnuCobol is not for use with zOS Cobol applications. Especially those applications that have been ported to Windows. Can you two try to be a wee bit more responsive. This SourceForge development process is unlike any kind of development effort I have ever partaken of. On one hand there exist great expertise. On the other hand many many novice level personnel. IMHO this is not anywhere near a collective development group. It must have been in the past - now it is really fragmented and unresponsive - with a hint of the experts no longer involved. Please respond to the issue I have documented below. Thank you. Ralph Attached
is a program fileprob.cob. When
compiled with -fassign=ibm both files open successfully. When
compiled without -fassign= When
compiled with -fassign=mf When
compiled with -fassign=cobol200 (cobc indicates this a valid
value) If
I change the ASSIGN TO clauses to be ASSIGN TO SYSUT1, ASSIGN TO
SYSUT2 C:\GEDIT\COBOL>fileprob I
thought I had this solved with -fassign-ibm Broken ? Please
advise |
FILEPROB.COB
Description: Text document
EXMPFILE.COB
Description: Binary data
[Prev in Thread] | Current Thread | [Next in Thread] |