Simon Sobisch

configure and other generated files aren't part of the repository since... GC 1.1 or so. You have two options: 1) build from version control -> after checkout/clone/download execute autogen.sh (creates the additional files, needs more tools - see HACKING for the list); this works with any version (also older ones or "tags") 2) get a nightly tarball (or even binary), the places to look for are https://sourceforge.net/projects/gnucobol/files/gnucobol/nightly_snapshots/ and nowadays also the OCamlPro...

Of course there are hallucinations and missing information in that LLM generated text... there is no libcob.conf but runtime.cfg there is no COB_EBCDIC_OVERRIDE runtime parameter, instead there is the CODE-SET clause in plain COBOL that can be used to do on-the-fly conversion the file part and the general post miss to note the different collating sequence - which again are both possible to explicit code in COBOL (and with GnuCOBOL 3.x+ also possible to pass on the command line / dialect configuration)...

It all depends what license concerns you have (just my understanding, consult your lawyer if the business depends on it): if you use GnuCOBOL only for your in-house software - there's no problem with using AGPL ever, no matter how you use it (it is your code and you are your only customer for that software) if you use it to provide a web frontend to customers then you'd have to make the code ( everything using that) available via that frontend as well - no problem for BDB+GnuCOBOL+dependencies, but...

It seems this ticket has been "lost" on the way. We found out that there's no "very easy" solution as we have to consider both the DEBUG-ITEM stuff and same field names but a different reference (occurs). Do you want to come back to this or should we end our findings with "we'd generate one seldom (COBOL-code), but unnecessary memmove less - but need to add a bunch of code for doing so" and close this ticket? Even if we do so... do we have useful tests that we can add to cover the current code better...

@dhugonnard this patch is unrelated to this ticket - if we don't have it in another place please post it whereever it is appropriate

Just a note: @OPTIONS directive from Fujitsu is also "kind of supported" (I think it currently is just ignored, but adding support for the ones we have CBL or $ or >> support for is "only some tedious work of mostly copy+paste" ) - you hopefully find something in our testsuite for that. ... speaking of where to get data: how was the CDF-CBL list info resolved? Does anyone know if the MF dollar list is complete? Checking for possible missing items likely means inspecting ppparse.y (and pplex.l).....

Feel free to do so (note: having at least a "hint" here is always good, as GitHub will only be a mirror - but learning git + PR workflows is good, as that will be nearly identical when we migrate from here to codeberg late[r] this year). I hope to get back to the PRs (and other open issues) when some of the load at work is down again.

Thanks for letting me know - obviously default keyboard layouts on Windows for Italy don't have that character - but not even the tilde? Both are parts of ASCII 7 bit, so that comes as a surprise. Backtick is classically used on any *nix as that creates a subshell and the tilde is the home directory, so also used often. Seems like https://github.com/ilpianista/itlinux-win-keyboard fixes both with the expected AltGr shortcuts.