Re: Char To ASCII

• To: info-dylan@ai.mit.edu
• Subject: Re: Char To ASCII
• From: Tom Emerson <tree@tiac.net>
• Date: Mon, 13 Mar 2000 13:02:30 -0500 (EST)
• In-reply-to: <Pine.GSO.3.96.1000312193936.29848B-100000@tardis.tardis.ed.ac.uk> (message from Hugh Greene on Sun, 12 Mar 2000 14:45:03 -0500 (EST))
• References: <XhCy4.374$SRc1.1507367@news.xtra.co.nz> <brucehoult-1203001550280001@bruce.bgh> <Pine.GSO.3.96.1000312193936.29848B-100000@tardis.tardis.ed.ac.uk>
• Sender: owner-info-dylan@ai.mit.edu

On Sun, 12 Mar 2000 14:45:03 -0500 (EST), Hugh Greene <q@tardis.ed.ac.uk> said:
> Note that, although this is probably portable across all current
> implementations, there's no *DRM-conformant* way to do this.  The
> DRM specifies that methods from <character> to <integer> and back
> exist but leave the behaviour undefined: they could use, say, EBCDIC
> and still be compliant ;-) Dylan really needs a better story about
> characters, particularly Unicode ...
[snip]

After a hiatus caused by a new job, I'm finally back to working on GD,
specifically its Unicode and other i18n support.

I'm going back over an exchange I had with Kim Barrett a long while
back concerning the original design goals for including Unicode in
Dylan.

Before Harlequin shut down I had some discussions with Jonathan
Bachrach about the expansion of the char type in Harlequin Dylan ---
hopefully I'll be able to start those up again as well.

          -tree

-- 
Tom Emerson, tree@tiac.net
http://www.tiac.net/users/tree
http://www.basistech.com/tree

• Char To ASCII
• From: "Brett Sheeran" <bsheeran@xtra.co.nz>
• Re: Char To ASCII
• From: brucehoult@pobox.com (Bruce Hoult)
• Re: Char To ASCII
• From: Hugh Greene <q@tardis.ed.ac.uk>

• Prev: Re: How can I..
• Next: Re: Dylan Newbie just wanting to say hi.
• Index(es):
  • Main
  • Thread