Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!agate.berkeley.edu!cgd
From: cgd@crucifixion.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.os.386bsd.development
Subject: Re: 16 bit implications (Re: 7bit unclean considered harmfull (was: Re: Need your opinion (TTYDEF ))8-bit clean state))
Date: 17 Jun 93 21:55:26
Organization: Kernel Hackers 'r' Us
Lines: 34
Message-ID: <CGD.93Jun17215526@crucifixion.CS.Berkeley.EDU>
References: <1993Jun14.081754.18248@alf.uib.no> <1vi6ak$hs7@umd5.umd.edu>
<1vigdl$ne0@sax.sax.de> <C8n7wp.62D@sugar.NeoSoft.COM>
<1993Jun16.154152.5624@gmd.de>
NNTP-Posting-Host: crucifixion.cs.berkeley.edu
In-reply-to: veit@mururoa.gmd.de's message of Wed, 16 Jun 1993 15:41:52 GMT
In article <1993Jun16.154152.5624@gmd.de> veit@mururoa.gmd.de (Holger Veit) writes:
|> Will this require making the characters 32 bits in the input queue, to allow
|> out of band info?
>
>For Heaven's sake, there are more clever mechanisms we (*) want to have.
>The discussion is about 16bit systems first, i.e. Unicode (although this is not
>the only way to do it), not ISO-10646 or other 32 bit systems.
Peter'ss not asking about the *character* representation, he's
asking about things like (from sys/tty.h):
#define TTY_QUOTE 0x00000100 /* Character quoted */
currently, we've got 8bit chars, and therefore need a 16-bit
data type in the ring buffer code.
if you've got 16bit chars, will we need a 32-bit data type in the
ring buffer code? unless you do something nasty, we will...
chris
--
Chris G. Demetriou cgd@cs.berkeley.edu
"386bsd as depth first search: whenever you go to fix something you
find that 3 more things are actually broken." -- Adam Glass