From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 2002:ac8:ec7:: with SMTP id w7mr11208206qti.197.1590789434985;
 Fri, 29 May 2020 14:57:14 -0700 (PDT)
X-Received: by 2002:aca:57d7:: with SMTP id l206mr2989094oib.84.1590789434749;
 Fri, 29 May 2020 14:57:14 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.uzoreto.com!tr2.eu1.usenetexpress.com!feeder.usenetexpress.com!tr3.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Fri, 29 May 2020 14:57:14 -0700 (PDT)
In-Reply-To: <raqqgu$nss$1@dont-email.me>
Complaints-To: groups-abuse@google.com
Injection-Info: google-groups.googlegroups.com; posting-host=47.185.215.60;
 posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo
NNTP-Posting-Host: 47.185.215.60
References: <50711230-5b14-4278-b9d8-d197bbe3c93b@googlegroups.com>
 <rapqt9$189k$1@gioia.aioe.org> <yS_zG.337746$mf1.50060@fx45.iad>
 <raqqgu$nss$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <85d07cd3-8f7b-4e19-81a9-397b53166b3d@googlegroups.com>
Subject: Re: Ada++
From: Optikos <ZUERCHER_Andreas@outlook.com>
Injection-Date: Fri, 29 May 2020 21:57:14 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader01.eternal-september.org comp.lang.ada:58871
Date: 2020-05-29T14:57:14-07:00
List-Id: <comp.lang.ada>

On Friday, May 29, 2020 at 6:09:20 AM UTC-5, bj=C3=B6rn lundin wrote:
> Den 2020-05-29 kl. 04:57, skrev Rick Newbie:
> > The curly braces are definitely not a problem
>=20
> If you ever lost one in the middle, you know that they ARE a problem
>=20
> end if/end case /end proc-name /end func.name /end package name /end=20
> loop etc
> makes it much easier too see where somehing ends
>=20
> switch (a)
> {
>     case 1 :
>      {
>        if (B=3D=3DC)
>        {
>           while (true)
>           {
>             doSometing1();
>             done =3D doSometing2();
>             if done break;
>           }
>        }
>     }
> }
>=20
> compared to
>=20
> case a is
>    when 1 =3D>
>      if B =3D C then
>        loop
>           Do_Someting1;
>           Done :=3D Do_Someting2;
>           exit when Done;
>        end loop;
>      end if;
>    when others =3D> null;
> end case;
>=20
>=20
> --=20
> Bj=C3=B6rn

Well, to be fair, C and its progeny have botched the original BCPL block-st=
atement bracketing hints.

https://dl.acm.org/doi/pdf/10.1145/988131.988138

As depicted in the article above, the BCPL feature applied to C would be th=
e following, including compile-time enforcement to assure that the programm=
er-chosen bra tags match the programmer-chosen ket tags (where bra-ket is s=
lang for open bracket and close bracket).

switch (a)
{sa
    case 1 :
     {c1
       if (B=3D=3DC)
       {ifBC
          while (true)
          {wT
            doSometing1();
            done =3D doSometing2();
            if done break;
          }wT
       }ifBC
    }c1
}sa

As also mentioned in the above-linked article, PL/I had an analogous label-=
based mechanism for
LBL: block-statement here END LBL;
which, btw, Green-Ada partially borrowed due its limited amount of competit=
iveness with Red-PL/I.