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 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,24d7acf9b853aac8
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII
Path: 
 g2news1.google.com!news4.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "(see below)" <yaldnif.w@blueyonder.co.uk>
Newsgroups: comp.lang.ada
Subject: Re: S-expression I/O in Ada
Date: Mon, 09 Aug 2010 20:35:01 +0100
Message-ID: <C88616F5.14C9B0%yaldnif.w@blueyonder.co.uk>
References: <547afa6b-731e-475f-a7f2-eaefefb25861@k8g2000prh.googlegroups.com>
  <osztlhozsld6.cnzz5m4w13ts.dlg@40tude.net>
 <bd4cba52-3e2c-4160-89bd-1f460271bcf9@5g2000yqz.googlegroups.com>
  <46866b8yq8nn$.151lqiwa0y2k6.dlg@40tude.net>
 <13b07f2c-2f35-43e0-83c5-1b572c65d323@y11g2000yqm.googlegroups.com>
  <13tpf7ya3evig$.h05p3x08059s$.dlg@40tude.net>
 <ee8ec904-60c1-405d-925f-89eba34a44d0@l20g2000yqm.googlegroups.com>
  <wccvd7l86f4.fsf@shell01.TheWorld.com>
 <1omt2srxtpsga$.c3hbxthzo6cf.dlg@40tude.net>
  <wcc4of4ub1x.fsf@shell01.TheWorld.com>
 <1e4cch2df5uyb.18brqdd16dhv8.dlg@40tude.net>
  <wccd3tsizh9.fsf@shell01.TheWorld.com>
 <cba4ng6r4ko9$.158m00g3j3x2a.dlg@40tude.net>
  <wcc7hjzzylp.fsf@shell01.TheWorld.com>
 <14y70ke8am9qw$.2csc9eflvigg.dlg@40tude.net>
  <4c601b5c$0$7665$9b4e6d93@newsspool1.arcor-online.net>
 <d8933d54-7fee-4923-8a0c-ce9c5b1b9383@14g2000yqa.googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: individual.net mYCqDyJXdyOBAuzNC+wVUQOnqcNj+aPB2NzRpwo0dsKnJ+i4Ma
Cancel-Lock: sha1:FNipOcf+8ypVXezBd5PWd236bXo=
User-Agent: Microsoft-Entourage/12.23.0.091001
Thread-Topic: S-expression I/O in Ada
Thread-Index: Acs3+fUtm63q/yCAG0Oa7WY2lHfIDA==
Xref: g2news1.google.com comp.lang.ada:13013
Date: 2010-08-09T20:35:01+01:00
List-Id: <comp.lang.ada>

On 09/08/2010 19:32, in article
d8933d54-7fee-4923-8a0c-ce9c5b1b9383@14g2000yqa.googlegroups.com, "Natacha
Kerensikova" <lithiumcat@gmail.com> wrote:

> On Aug 9, 5:14�pm, Georg Bauhaus <rm.dash-bauh...@futureapps.de>
> wrote:
>> On 09.08.10 16:38, Dmitry A. Kazakov wrote:
>> 
>>> Just one example from a huge list, why "in" is not an operation?
>> 
>>> � �if 0 /= (Mode and Alarm) then �-- Isn't it awful?
>> 
>>> why am I not allowed to have:
>> 
>>> � �if Alarm in Mode then
>> 
>> Is anything wrong with packed arrays of Booleans for status thingies?

I define a function "/" that takes the types of Mode and Alarm and returns
Boolean, so I can say things like:

   if Alarm/Mode then ...

Or (real code)

   if INS.jump_target/starts_a_code_block  then ...

-- 
Bill Findlay
<surname><forename> chez blueyonder.co.uk