Activity for Cobxref
-
Vincent (Bryan) Coen posted a comment on discussion General Discussion
Update v2.03.15 has been uploaded to the file area. This fixes bugs where cobxref processes verb CALL where there is a reserved word pre routine name such as STATIC or STDCALL where these reserved words would be used instead of the routine. I have tried to update the SVN system but keep getting a message that the first file being commited is out of date and it is not. I cannot see a way of fixing this issue. That said the current version is present in the GnuCobol contrib area - that works.
-
Cobxref released /cobxref-2.03.15.zip
-
Version 2.03.12 -> v2.04, hopefully will be released in a few weeks / month, once some bugs have been traced and fixed. This introduces facilities for nested programs to have GLOBAL, EXTERNAL and CDF DEFINEs etc showing up in the right places in the xref listings. Note that an END PROGRAM | FUNCTION terminates any CDF DEFINEs (>>DEFINE or $SET DEFINE for that program as the compiler should be doing at least according to @Simon. Of course, this does NOT apply to the use of GLOBAL or EXTERNAL for files...
-
Processing GLOBAL and EXTERNAL referencing
-
CDF Support
-
Processing GLOBAL and EXTERNAL referencing
-
manual update
-
I am pleased to announce V2.03.05 has been released today directly here and in GC contribs. This version will now remove the CDF >>DEFINE | SET vars from the Global table when reading an END PROGRAM statement. A extra error message has been added if the Global count after remove said CDF words means that the count is negative and no it should not happen: Also cleaned up msg3 - 6 by putting them in correct logical order - the manual has been so updated. svn has been updated with the files changed...
-
-
2.03.05
-
Referring to post 2022-03-27 version is updated to v2.03.05 where some code was added to support tidying up the issue with CDF >>DEFINE and >>SET for the git table but as no one has commented or complained about this functionality it has not been progress further. I.e, any CDF >>DEFINE etc set at the top of a nest program group will remain in effect for all nested programs. As very few programmers make use of the nested program feature this issue is not likely to come up, although I do make use of...
-
cobxref updated source file for v2.03.05 missed Changelog update & vers error
-
cobxref updated source file for v2.04.05
-
One very minor problem has come to pass in that : When using the CDF statements >>DEFINE and >>SET with CONSTANT cobxref transfers these to the GIT (Global/External) table as soon as it finds them - so far so good. It then uses them by adding them into the sort input file, runs sort then produces the source and xref listings etc I have now found out that both of these CDF statements are only in scope up to the point of an END PROGRAM progname statement when they are terminated. cobxref does no such...
-
One very minor problem has come to passin that : When using the CDF statements >>DEFINE and >>SET with CONSTANT cobxref transfers these to the GIT (Global/External) table as soon as it find them - so far so good. It then uses them by adding them into the sort input file, runs sort then produces the source and xref listings etc I have now found out that both of these CDF statements are only in scope up to the point of an END PROGRAM progname statement when they are terminated. cobxref does no such...
-
Updated README and added cobxref-README
-
CDF Support
-
Completed as of v2.03.04 dated 27th March 2022. All known bugs fixed including one or two spotted during testing mostly created by previous bug fixes but not found.
-
Update v2.03.04 - 27th March 2022 All known bugs cleared, including duplicate reference numbers, for same variable. Included support for CDF statements : DEFINE CONSTANT SET CONSTANT Increased the number of referenced occurrences per report line from 8 to 12 and added a total reference count per variable to make it easier for testing against other cross reference programs including the internal one. Included feature to produce both block xref lists at end of program and the normal one by group, section...
-
Cobxref v2.03.04 Feature updates & bugfixes
-
-
Update v2.02.04 - December 2021. Bug found by David Wall in zz180-Check-For-Param-Errors where a perform search was using 128 for a field that is only 64 characters and that produced a runtime out of bounds error. At some point I changed the size but did not find in all other testing, but it may be, he had -g (runtime checks) set for during the compile. Thanks, David. In bc000-Test-For-Missing-Replace and when running with -g, produces a runtime failure so now checking if not > 1 in bc000-Test-For-Missing-Replace....
-
Fixed so should get posted messages now.
-
Sorry for delay, only just spotted this post. printcbl does exist, and it is the Contribution section for GnuCOBOL on SF under SVN, contributions, trunk, tools, near the bottom of the list. The source for printcbl is also included within cobxref as a nested program with minor changes to let it work within a called process etc namely cobxref.. There is more than one nested program within cobxref. Must check why I am not being notified of a post!
-
CDF Support
-
-
Tidy
-
Update to README & TODO
-
Cobxref 2.03.04 update for bugs
-
CDF Support
-
red posted a comment on discussion General Discussion
Does printcbl.cbl exist or has this been absorbed in the xref functionality? I am working on a cobol project and printcbl.cbl would be helpful to me. Thanks
-
CDF Support
-
Updated cobxref manual
-
Home
-
Update v2.02.03 fixes a small but significant error when source program has >>SOURCE statement in the wrong column such as cc9 and is ignored when cobxref is run without -free parameter. This error caused a msg2 error as cobxref was trying to use FIXED format to read a free format source. SVN and archive has been uploaded.
-
Sorry only just seen this msg, I have adjusted my setting for the discussion area. Using the latest cobxref sources (2.02.03) see file area AND changing your COPY statement as the compiler did not like it running under Linux to all upper case as the CPY file is and then recompiling your program (without errors) I ran cobxref with no issues. Any sources used with cobxref MUST run through cobc without errors first.
-
Cobxref v2.02.03 bug fix for finding >>SOURCE in wrong CC
-
-
Michael Simpson posted a comment on discussion General Discussion
Am trying to run COBXREF on a very small program and am getting the above error. Any suggestions. I'll attach the source code and the one copybook used.
-
v2.02.02 update and manual
-
Update v2.02.02 fixes a small problem with an updated manual - nothing heavy. See files section.
-
Update v2.02.02 fixes a small problem with an updated manual - nothing heavy. See files ection.
-
-
A new version has been released as v2.02..01 this covers: Bug fix for report page numbering with odd values after the count reaches 127 - due to a data field as binary-char, changed to binary-long. This will cover large program listings along with one containing nested programs. Support for user words of up to a length of 63 characters where used for data, section, paragraph, program and module / function names. This has only been tested against cobxref itself which does not have words beyond current...
-
Update to v2.02.01 support for long user names (63 char)
-
-
Adding Cobxref manual
-
-
Cobxref update for Lead/Trail
-
The new version of cobxref has been release and uploaded to sourceforge as v2.01.01. This supports fixed and free format and COPY verb down nine levels with all reportedand found bugs fixed . As it uses a version of printcbl to do the processing of the COPY CDF facility that too has been updated along with various bug fixes so that the two are inline with each other as much as possible. It has been tested against some 1,000 productions programs including some that are over 40,000 lines long as well...
-
The new version of cobxref has been release and uploaded to sourceforge as v2.01.01. This supports fixed and free format and COPY verb down nine levels with all reportedand found bugs fixed . As it uses a version of printcbl to do the processing of the COPY CDF facility that too has been updated along with various bug fixes so that the two are inline with each other as much as possible. There has not been any changes to the MVS version as that ony uses fixed format sources. .
-
Cobxref README file update
-
Cobxref README file update
-
Cobxref v2.01.01 major Update
-
-
Forgot to add - this new version does/or not: Is an independent program - it is not callable from the compiler - all such code is being removed. It is run using standard commands such as: cobxref sfn.cbl sfn.lst -FREE | -free | -FIXED | - fixed It will create additional files - sfn.lst - source listing plus xref reports. sfn.pco - contains all expanded copy books) - Can be deleted after EOJ. Part1.tmp created in your ./tmp directory - These are used for sort processing . Part2.tmp and may be deleted...
-
Progress - Tested with basic COPY verbs (no replacing) for free format all ok. Tested with copy replacing using var by var for free format all ok. Thats the good news as copy replacing using the ==abcd== by ==efg== is broken. Once solved then testing again but using fixed format. During testing found bugs in Printcbl in various areas and these have been fixed as for cobxref but again the repacing ==abcd== etc is broken and not tested yet fixed format. Yes that means I an testing both cobxref and...
-
Currently working on a update to provide support for copy library inclusion via the COPY verb. Taken a lot longer than expected and still a mess but now considering using a modified version of printcbl that is included with the source to preprocess a user supplied Cobol source file creating a temporary source file which is input to cobxref for processing. This provides up to nine levels of COPY processing that is a copy calling a copy calling a copy etc and this includes the original source file....
-
Aoirthoir An Broc posted a comment on discussion General Discussion
Hello to you too! Will be participating here as I start to get back into COBOL again....
-
-
-
Total refresh+commit
-
Total refresh+commit
-
I have issued a new version for the MVS 3.8J platform. This works with Turnkey 4...
-
-
-
-
Hello to the general discussion area. Covers just about anything including any issues...
-
-
-
-
-
-
-
1
