• Re: oThe end of software secrecy is almost upon

    From Jerry Brown@jerry@jwbrown.co.uk.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 08:11:01 2026
    From Newsgroup: comp.lang.c++

    On Sat, 24 Oct 2026 21:38:43 GMT, Charlie Gibbs
    <cgibbs@kltpzyxm.invalid> wrote:

    On 2026-10-24, Scott Dorsey <kludge@panix.com> wrote:

    Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    Still, somebody had to decide to make the MS-DOS COPY command refuse
    to copy zero-length files - something which CP/M's PIP did happily.

    That's a bug and not a feature. Sometimes you want to have a zero-length
    file in place as a semaphore.

    Exactly. Another case is a month-to-date accumulator
    at the beginning of the month.

    Still, I've heard some pretty amazing attempts to justify this
    design flaw as a feature.

    I supported an IBM 9370 back in the 90s and whatever operating system
    it ran (completely different to the 3090 mainframe with JCL, etc it
    was supposed to replace) didn't allow zero length files.
    --
    Jerry Brown

    A cat may look at a king
    (but probably won't bother)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Koenig@tkoenig@netcologne.de to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 09:30:12 2026
    From Newsgroup: comp.lang.c++

    Jerry Brown <jerry@jwbrown.co.uk.invalid> schrieb:

    I supported an IBM 9370 back in the 90s and whatever operating system
    it ran (completely different to the 3090 mainframe with JCL, etc it
    was supposed to replace) didn't allow zero length files.

    VM/CMS?
    --
    This USENET posting was made without artificial intelligence,
    artificial impertinence, artificial arrogance, artificial stupidity,
    artificial flavorings or artificial colorants.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 08:37:51 2026
    From Newsgroup: comp.lang.c++

    On 10/25/26 02:30, Thomas Koenig wrote:
    Jerry Brown <jerry@jwbrown.co.uk.invalid> schrieb:

    I supported an IBM 9370 back in the 90s and whatever operating system
    it ran (completely different to the 3090 mainframe with JCL, etc it
    was supposed to replace) didn't allow zero length files.

    VM/CMS?


    Or some version of DOD/360? They had a couple of versions, I think. They
    kept trying to make it easier to install and maintain, but it was still DOS.

    Those times I want to run something now I use VM, because it is so much simpler.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 08:42:16 2026
    From Newsgroup: comp.lang.c++

    On 10/25/26 08:37, Peter Flass wrote:
    On 10/25/26 02:30, Thomas Koenig wrote:
    Jerry Brown <jerry@jwbrown.co.uk.invalid> schrieb:

    I supported an IBM 9370 back in the 90s and whatever operating system
    it ran (completely different to the 3090 mainframe with JCL, etc it
    was supposed to replace) didn't allow zero length files.

    VM/CMS?


    Or some version of DOD/360? They had a couple of versions, I think. They kept trying to make it easier to install and maintain, but it was still
    DOS.

    Those times I want to run something now I use VM, because it is so much simpler.

    DOS, sorry typo.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jerry Brown@jerry@jwbrown.co.uk.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 07:59:39 2026
    From Newsgroup: comp.lang.c++

    On Sun, 25 Oct 2026 09:30:12 -0000 (UTC), Thomas Koenig
    <tkoenig@netcologne.de> wrote:

    Jerry Brown <jerry@jwbrown.co.uk.invalid> schrieb:

    I supported an IBM 9370 back in the 90s and whatever operating system
    it ran (completely different to the 3090 mainframe with JCL, etc it
    was supposed to replace) didn't allow zero length files.

    VM/CMS?

    That's ringing a vague bell.

    My time on the 9370 was short compared to the 3090, so all I can
    remember were things like the file handling was MUCH simpler (no need
    specify record types and block sizes and the foreground scripting
    language REXX was much nicer than the CLIST we used on the mainframe -
    it had stacks for storing and processing data, which was fun.

    The only command I can remember was when I had my operator hat on and
    a user wanted to access the 3422 tape drive I had to ATTACH the
    physical 3 digit id of the tape drive to the logical 3 digit id they
    were using (in retrospect I see this was its equivalent of unix mount
    command).
    --
    Jerry Brown

    A cat may look at a king
    (but probably won't bother)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 10:33:22 2026
    From Newsgroup: comp.lang.c++

    In article <5e1udl9hs8733aqpjenq0vk71v3pn25q8n@jwbrown.co.uk>,
    Jerry Brown <jerry@jwbrown.co.uk.invalid> wrote:
    On Sun, 25 Oct 2026 09:30:12 -0000 (UTC), Thomas Koenig ><tkoenig@netcologne.de> wrote:

    Jerry Brown <jerry@jwbrown.co.uk.invalid> schrieb:

    I supported an IBM 9370 back in the 90s and whatever operating system
    it ran (completely different to the 3090 mainframe with JCL, etc it
    was supposed to replace) didn't allow zero length files.

    VM/CMS?

    That's ringing a vague bell.

    My time on the 9370 was short compared to the 3090, so all I can
    remember were things like the file handling was MUCH simpler (no need
    specify record types and block sizes and the foreground scripting
    language REXX was much nicer than the CLIST we used on the mainframe -
    it had stacks for storing and processing data, which was fun.

    The only command I can remember was when I had my operator hat on and
    a user wanted to access the 3422 tape drive I had to ATTACH the
    physical 3 digit id of the tape drive to the logical 3 digit id they
    were using (in retrospect I see this was its equivalent of unix mount >command).

    That sounds like VM/ESA, all right. Command list `LIST` and
    `TYPE` and a three-field file name relative to a "minidisk"?
    REXX was the "usual" scripting language.

    VM was kind of neat.

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rosario19@Ros@invalid.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 10:54:42 2026
    From Newsgroup: comp.lang.c++

    On Tue, 20 Oct 2026 20:20:39 -0000 (UTC), Lawrence D|+Oliveiro wrote:

    On Tue, 20 Oct 2026 15:06:48 -0500, Lynn McGuire wrote:

    The key to writing any software is lots of commenting.

    A key point about comments is they should explain *why* the code is

    the win for comment it is when code explain itself with 0 comment
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rosario19@Ros@invalid.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 10:58:51 2026
    From Newsgroup: comp.lang.c++

    On Tue, 20 Oct 2026 16:40:47 -0400, Cryptoengineer wrote:

    On 10/20/2026 2:22 PM, Scott Dorsey wrote:
    In article <11b8b2k$p44i$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >>> Cryptoengineer <petertrei@gmail.com> wrote:
    Edgar Dijkstra: Go To Statement Considered Harmful

    A man who clearly never programmed in assembler.

    I have seen a structured assembler class and it's actually not a bad way
    to think at all. Having LOOPZ and REP* and similar instructions make it
    easier to think about do loops.

    The key to writing structured assembly is commenting.

    The key to writing [] assembly is commenting.

    no it is the right code easy to understand
    comment can be avoid if someone use meaning varible (even if one char
    b= buffer, b=binary b=ebx ecc)

    Fixed That For You.

    pt


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Fred. Zwarts@F.Zwarts@HetNet.nl to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 11:11:40 2026
    From Newsgroup: comp.lang.c++

    Op 02.nov.2026 om 10:54 schreef Rosario19:
    On Tue, 20 Oct 2026 20:20:39 -0000 (UTC), Lawrence D|+Oliveiro wrote:

    On Tue, 20 Oct 2026 15:06:48 -0500, Lynn McGuire wrote:

    The key to writing any software is lots of commenting.

    A key point about comments is they should explain *why* the code is

    the win for comment it is when code explain itself with 0 comment

    Code can only explain what it does, what the algorithm is.
    Code cannot explain why that algorithm was chosen. That is where
    comments are for.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 16:51:46 2026
    From Newsgroup: comp.lang.c++

    On 2026-11-02, Fred. Zwarts <F.Zwarts@HetNet.nl> wrote:

    Op 02.nov.2026 om 10:54 schreef Rosario19:

    On Tue, 20 Oct 2026 20:20:39 -0000 (UTC), Lawrence D|+Oliveiro wrote:

    On Tue, 20 Oct 2026 15:06:48 -0500, Lynn McGuire wrote:

    The key to writing any software is lots of commenting.

    A key point about comments is they should explain *why* the code is

    the win for comment it is when code explain itself with 0 comment

    Code can only explain what it does, what the algorithm is.
    Code cannot explain why that algorithm was chosen. That is where
    comments are for.

    Unfortuately, a lot of people (especially CS weenies) love to
    loudly proclaim, "My code is so readable that no comments are
    necessary!" (Sometimes they apply this argument to their choice
    of programming language as well.) They're usually wrong.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 20:06:53 2026
    From Newsgroup: comp.lang.c++

    On Mon, 02 Nov 2026 16:51:46 GMT, Charlie Gibbs wrote:

    Unfortuately, a lot of people (especially CS weenies) love to loudly proclaim, "My code is so readable that no comments are necessary!"

    WasnrCOt that the argument made by the rCLbusinessrCY users for COBOL? That
    the language was practically English anyway ... ?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rosario19@Ros@invalid.invalid to comp.lang.c++ on Fri Nov 6 12:43:08 2026
    From Newsgroup: comp.lang.c++

    On Tue, 20 Oct 2026 23:18:44 GMT, Charlie Gibbs wrote:
    On 2026-10-20, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Tue, 20 Oct 2026 19:04:55 GMT, Charlie Gibbs wrote:

    The undisciplined use of GOTOs is bad, agreed.

    Is there such a thing as a *disciplined* use of gotos?

    Yes, especially in COBOL or assembly language. For instance,
    a GOTO to the end of a function ensures any of its cleanup code
    gets executed, and fulfils a goal of structured proramming:
    each function has one exit point.

    I find the C code I write tends to do a lot of dynamic resource
    allocations. These can sometimes fail with errors. So error recovery
    will invariably involve cleaning up those parts of the allocations
    which already succeeded.

    Gotos are no good for this; you need to exit
    levels of structure nesting one by one, disposing of allocations as
    you go.

    If in the start of the function all pointer are NULL, and in the end
    of the function there are all the free()
    I not have find all your problems with possibly multiple goto that
    point to the end of the function
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.c++ on Fri Nov 6 16:38:28 2026
    From Newsgroup: comp.lang.c++

    On Fri, 06 Nov 2026 12:43:08 +0100
    Rosario19 <Ros@invalid.invalid> gabbled:
    On Tue, 20 Oct 2026 23:18:44 GMT, Charlie Gibbs wrote:
    On 2026-10-20, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Tue, 20 Oct 2026 19:04:55 GMT, Charlie Gibbs wrote:

    The undisciplined use of GOTOs is bad, agreed.

    Is there such a thing as a *disciplined* use of gotos?

    Yes, especially in COBOL or assembly language. For instance,
    a GOTO to the end of a function ensures any of its cleanup code
    gets executed, and fulfils a goal of structured proramming:
    each function has one exit point.

    I find the C code I write tends to do a lot of dynamic resource
    allocations. These can sometimes fail with errors. So error recovery
    will invariably involve cleaning up those parts of the allocations
    which already succeeded.

    Gotos are no good for this; you need to exit
    levels of structure nesting one by one, disposing of allocations as
    you go.

    If in the start of the function all pointer are NULL, and in the end
    of the function there are all the free()
    I not have find all your problems with possibly multiple goto that
    point to the end of the function

    This is also a reason the only-one-exit-point nonsense mentioned above is a Very Bad Idea unless its a simple function because you may have to do a load
    of checks that wouldn't be required if the flow of control left at an earlier point. Also with too much block nesting it becomes unreadable even in the best IDEs.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rosario19@Ros@invalid.invalid to comp.lang.c++ on Sat Nov 7 13:35:34 2026
    From Newsgroup: comp.lang.c++

    On Mon, 02 Nov 2026 16:51:46 GMT, Charlie Gibbs wrote:
    On 2026-11-02, Fred. Zwarts <F.Zwarts@HetNet.nl> wrote:

    Op 02.nov.2026 om 10:54 schreef Rosario19:

    On Tue, 20 Oct 2026 20:20:39 -0000 (UTC), Lawrence D|+Oliveiro wrote:

    On Tue, 20 Oct 2026 15:06:48 -0500, Lynn McGuire wrote:

    The key to writing any software is lots of commenting.

    A key point about comments is they should explain *why* the code is

    the win for comment it is when code explain itself with 0 comment

    Code can only explain what it does, what the algorithm is.
    Code cannot explain why that algorithm was chosen. That is where
    comments are for.

    Unfortuately, a lot of people (especially CS weenies) love to
    loudly proclaim, "My code is so readable that no comments are
    necessary!" (Sometimes they apply this argument to their choice
    of programming language as well.) They're usually wrong.

    I m not a too much code writer
    until now, making some test I can understand and can correct bug on my
    code even if not commented enought (but input variable and output
    variable of one function are always/ should always be commented). code difficult as printf like functions, malloc, bignum function operators
    etc in assembly too.

    On others code i suspect it would be difficult for me even if
    commented... the indentation and names of variable are one easy way of
    comment code (i read that in a book speak on pascal language), without
    write one line of comment. Writing always the same type of loop, the
    same type of inizialization in the same position, the same names, I
    can figure out all soon...


    --- Synchronet 3.22a-Linux NewsLink 1.2