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=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.42.39.140 with SMTP id h12mr7966741ice.9.1406668519835;
        Tue, 29 Jul 2014 14:15:19 -0700 (PDT)
X-Received: by 10.182.104.138 with SMTP id ge10mr19986obb.37.1406668519569;
 Tue, 29 Jul 2014 14:15:19 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.glorb.com!h18no10072764igc.0!news-out.google.com!px9ni1igc.0!nntp.google.com!h18no6161702igc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Tue, 29 Jul 2014 14:15:19 -0700 (PDT)
In-Reply-To: <lyd2coqa87.fsf@pushface.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=173.57.209.48;
 posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo
NNTP-Posting-Host: 173.57.209.48
References: <lr674v$34l$1@speranza.aioe.org> <lr7ug2$ncr$1@dont-email.me>
 <af2a7f35-2149-444e-b2d0-8333841b1b13@googlegroups.com>
 <lyd2coqa87.fsf@pushface.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <32ca52c1-6073-4611-a18b-ec7a04b22805@googlegroups.com>
Subject: Re: What is a byte?
From: "Dan'l Miller" <optikos@verizon.net>
Injection-Date: Tue, 29 Jul 2014 21:15:19 +0000
Content-Type: text/plain; charset=ISO-8859-1
Xref: news.eternal-september.org comp.lang.ada:21342
Date: 2014-07-29T14:15:19-07:00
List-Id: <comp.lang.ada>

On Tuesday, July 29, 2014 1:40:56 PM UTC-5, Simon Wright wrote:
> "Dan'l Miller" writes:
> > ...  (No specification of any
> > modern interoperable protocol uses the 2^8 and higher bits in a byte
> > if they exist on some arcade hardware.)
> 
> I don't think this is right (not in terms of how the ABI expects a char
> to be passed to a function, but in terms of what Victor ought to do).
> 
> If the C function takes a char, you should specify
> Interfaces.C.char. It's up to the compiler to decide whether that gets
> passed in 8 bits, 32 bits, or come to that 9/36 bits on hardware that no
> one is remotely likely to encounter (even in an arcade).

That dang spell check has become my worst enema:  arcane, not arcade.