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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,a9bab26b6fe54a36 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Path: g2news2.google.com!postnews.google.com!w10g2000yqa.googlegroups.com!not-for-mail From: Shark8 Newsgroups: comp.lang.ada Subject: Re: Pondering what rationale behind record type Date: Tue, 10 May 2011 19:28:16 -0700 (PDT) Organization: http://groups.google.com Message-ID: <9543fcbd-9035-45d3-8a5b-45592f927685@w10g2000yqa.googlegroups.com> References: <90148303-4dc4-4c05-882f-88dd69a95494@z13g2000prk.googlegroups.com> <92quueFnsfU1@mid.individual.net> <4dc864b9$0$6890$9b4e6d93@newsspool2.arcor-online.net> <4dc90f7a$0$7659$9b4e6d93@newsspool1.arcor-online.net> <11dlfbvj00hru$.7zkw6im0a7gj$.dlg@40tude.net> <4dc92d14$0$6776$9b4e6d93@newsspool3.arcor-online.net> <14o3gst7h97px$.g6k9bn5b3p4q$.dlg@40tude.net> NNTP-Posting-Host: 24.230.151.194 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1305080896 14518 127.0.0.1 (11 May 2011 02:28:16 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 11 May 2011 02:28:16 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: w10g2000yqa.googlegroups.com; posting-host=24.230.151.194; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1,gzip(gfe) Xref: g2news2.google.com comp.lang.ada:20192 Date: 2011-05-10T19:28:16-07:00 List-Id: On May 10, 7:50=A0am, "Dmitry A. Kazakov" wrote: > > What is the reason to name statements? Simple: to aid in readability. I have a few rather deeply nested items where I'm tokenizing PostScript (due the rules of the language) and it is handy to have things like -- Case C, When C '<' =3D> Read_Character( C, Input ); HANDLE_LT: -- less than if C =3D '<' then Return Dictionary_Type; elsif C =3D '~' then Return String_Type; else Unread_Character( C, Input ); Return -- I forgot what the last case, just '<', was... end if HANDLE_LT; There's even a few in blocks where I handle things like names ['identifiers'] vs. numbers; the PLRM defines a name as a string of "regular characters which cannot be interpreted as a string." This means that 23E4 is a number while 24F4 is a name as are $4, 2i3, @, 2^4 and so forth. It REALLY does help in sorting where you are in the decoding.