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.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,92c39a3be0a7f17d X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-03-07 18:08:27 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!hub1.nntpserver.com!btnet-peer0!btnet-peer!btnet!news-hub.cableinet.net!blueyonder!psiuk-p2!psiuk-p3!uknet!psiuk-n!news.pace.co.uk!nh.pace.co.uk!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada Subject: Re: Future with Ada Date: Thu, 7 Mar 2002 11:25:20 -0500 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: References: <3C7B0B13.3080003@worldnet.att.net> <3C7D1C89.2000803@home.com> <3C7E7CAD.7070504@mail.com> <3C7FB9D2.D9C6E055@boeing.com> <3C81DF1F.9000503@mail.com> <3C83A112.6080302@mail.com> <3C84223C.A356F466@adaworks.com> <3C853A04.34826F39@despammed.com> NNTP-Posting-Host: dhcp-200-133.miami.pace.co.uk X-Trace: nh.pace.co.uk 1015518321 8402 136.170.200.133 (7 Mar 2002 16:25:21 GMT) X-Complaints-To: newsmaster@news.cam.pace.co.uk NNTP-Posting-Date: 7 Mar 2002 16:25:21 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Xref: archiver1.google.com comp.lang.ada:20924 Date: 2002-03-07T16:25:21+00:00 List-Id: In theory, this might be a really good idea. "If" statements that span too many lines (define "too many"?) or nest too deep (again, define "too deep"?) ought to be avoided. When possible, it should be refined to subprogram calls or whatever so that it doesn't get "too complicated". :-) But in practice, there will be times when an "if" statement or "case" statement is going to get beyond one screen's worth of lines and any attempt to shorten it up to fit within a screen is going to result in gyrations that make an unholy mess just to avoid "too many" or "too deep" as defined in some coding guideline. When an "if" or "case" gets longer than a single screen or contains within it another "if" or "case" (one level of nesting) I think it would be useful for any block of code that spans more than a single screen to have a label identifying what exactly is being ended when you hit the "end if" or "end case". One wouldn't need to use it if it seemed to be creating too much clutter, but there *will* be cases where two or three levels of nesting occur or 40 or 50 lines of code go by & knowing what the "end" connects with would be handy. MDC -- Marin David Condic Senior Software Engineer Pace Micro Technology Americas www.pacemicro.com Enabling the digital revolution e-Mail: marin.condic@pacemicro.com Web: http://www.mcondic.com/ "Georg Bauhaus" wrote in message news:a683ab$3ls$2@a1-hrz.uni-duisburg.de... > > If `end if something' will invite to have long chunks of code inside > the ifs, the idea should be banned. Sometimes Structured Programming > is really convincing. Ada is good at stepwise refinement _not_ using > ifs, but different language facilities. >