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 10.236.84.239 with SMTP id s75mr1756067yhe.28.1389823454134; Wed, 15 Jan 2014 14:04:14 -0800 (PST) X-Received: by 10.182.109.36 with SMTP id hp4mr14177obb.30.1389823454011; Wed, 15 Jan 2014 14:04:14 -0800 (PST) Path: border1.nntp.dca3.giganews.com!backlog4.nntp.dca3.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!news.glorb.com!p15no16593131qaj.0!news-out.google.com!gg4ni4085qab.0!nntp.google.com!6no12236704qao.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 15 Jan 2014 14:04:13 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=149.32.224.34; posting-account=Qh2kiQoAAADpCLlhT_KTYoGO8dU3n4I6 NNTP-Posting-Host: 149.32.224.34 References: <27ff7582-b2bd-4a51-80a9-6a65a8c3f38b@googlegroups.com> <74bb1a6c-4239-448b-aa0c-41684cc0fdf5@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <9e8a283e-997a-4409-ab3e-fe14a0904066@googlegroups.com> Subject: Re: Aspect CPU From: Anh Vo Injection-Date: Wed, 15 Jan 2014 22:04:14 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Original-Bytes: 2138 Xref: number.nntp.dca.giganews.com comp.lang.ada:184436 Date: 2014-01-15T14:04:13-08:00 List-Id: On Wednesday, January 15, 2014 12:00:26 PM UTC-8, Simon Wright wrote: > Anh Vo writes: > =20 > > By the way, do you mind to tell which > > section of RM showing this declarative syntax. > =20 > For tasks, 9.1(2), > http://www.ada-auth.org/standards/12rm/html/RM-9-1.html#p2 =20 Thanks Simon. It is obviously I overlooked this section. After looking at t= his section carefully, paragraph 6/3 invokes my curiosity. My question is w= hy aspect_specification is allowed in task body definition as paragraph 6/3= is repeated below for easy discussion. task_body ::=3D=20 task body defining_identifier [aspect_specification] is declarative_part begin handled_sequence_of_statements end [task_identifier]; Anh Vo