Newsgroups: comp.lang.dylan
Path: cantaloupe.srv.cs.cmu.edu!rochester!cornellcs!travelers.mail.cornell.edu!news.kei.com!news.mathworks.com!newsfeed.internetmci.com!news.msfc.nasa.gov!elroy.jpl.nasa.gov!swrinde!howland.reston.ans.net!ix.netcom.com!netcom.com!gperkins
From: gperkins@netcom.com (Glen C. Perkins)
Subject: dylan and unicode
Message-ID: <gperkinsDGysp7.9I5@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
Date: Tue, 24 Oct 1995 18:00:43 GMT
Lines: 20
Sender: gperkins@netcom.netcom.com

My favorite feature in Java is the fact that 'char' is no longer
just a funny spelling for the word 'byte', but is actually a
unicode character. Strings are then first-class objects composed
of these unicode chars. This means that in Java, I'm not going
to have to twist my code into a different-shaped pretzel for
each different language I want to support. All that nonsense of
some single-byte characters mixed with some double-byte mixed
with escape codes etc. is mostly gone from basic text manipulation
if you work in Java.

What about dylan? Is dylan also based on unicode or is there any
chance that it will become so? Global software markets are the
way of the future, and any development system that handles
some of the complexity automatically will stand a much greater
chance of survival.

__Glen__
-- 
+---------------------------------------------------------------------------+

