Simon Sobisch

Hi Aretwo and nice to "see" you with the note that cobc already works well for you for years - it is never too late to join the community :-) cobc actually says something different: it tries to compile something called "Hello" and something that is called "Fixelo.cob" with Hello containing binary data (a newer version of cobc is most likely already better to recognize the later). The reason for compiling the binary is rooted in COPY Hello. So what most likely happened is the following: a layout of...

Fix done by @rumii available at https://github.com/OCamlPro/gnucobol/commit/dab76ce13ac305ed261ebbce47a37cca7885c5ea.patch - will be checked in "soon" (likely after copyright papers are finished).

Fix available at https://github.com/OCamlPro/gnucobol/commit/dab76ce13ac305ed261ebbce47a37cca7885c5ea.patch - will be checked in "soon" (likely after copyright papers are finished).

Thanks for posting an English version - but that should really be part of the same post as your Spanish one, also if it is an updated version - so let's keep any discussion to [56252239cf] (you may edit your post there, then we can also delete this additional topic).

If you are learning then I highly recommend to go through the worldcities example (step by step extension of a program with needs and coding similar to tasks in production) and if anything is unclear while doing so (you'll highly benefit from the "step by step" approach) check the Programmer's Guide next to it.

It makes AI a senior expert in COBOL, Bash and banking Kafka. Reality check: It asks the LLM (we are far away from AI) to pretend to be that. Especially the COBOL part is hard for LLMs as their training data has commonly not many examples. It will therefore be "even more confident" to do things correct while inventing English sounding syntax that does not even exist. For programming languages it is commonly better for an LLM to be used as an agent with access (and instructions how to do so!) to a...

Hi Lucas and welcome to GnuCOBOL! Here's the review comment posted some minutes ago on GH, posting it possibly overlap with your post here. Thanks for the idea. Note that there is to be no ON OVERFLOW as all is DELIMITED BY SIZE - so the fixed size needs to be valid (we actually should have a warning if there is always an overflow and also use that to handle any exception code as "normal" condition in the compiler [= raise "always false/true" warnings - these and more musings in [feature-requests:#519])....

STRING / UNSTRING performance for literals + all DELIMITED BY SIZE