Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!bu.edu!transfer!lectroid!jjmhome!smds!rh From: rh@smds.UUCP (Richard Harter) Newsgroups: comp.lang.misc Subject: Re: What does an anti-perl look like Summary: Lakota character set Message-ID: <548@smds.UUCP> Date: 13 Jun 91 05:30:53 GMT References: <16867@helios.TAMU.EDU> <1991Jun05.013632.3198@convex.com> Organization: SMDS Inc., Concord, MA Lines: 25 In article , jbw@maverick.uswest.com (Joe Wells) writes: > In article <541@smds.UUCP> rh@smds.UUCP (Richard Harter) writes: > (A) Brutally stripped syntax. The only special characters are (){} and > the white space characters. There are no quote characters, no meta > characters and no escape character, and no need for them. > Does this mean that the NUL character (0) is treated like a letter? No - but it's an interesting thought. The character set is all printable characters. Special characters, in this context, are punctuation characters, characters used as operators, etc. For example, +-=,.[](){}!~&|$\ etc in the UNIX shell. It is a design spec that OS commands be legal Lakota commands, in so far as possible, i.e. a Lakota script can have a mixture of Lakota and UNIX shell commands under UNIX or Lakota and DCL under VMS. The stripped syntax is a consequence. For this purpose, Lakota is an extension language over the underlying OS command language; to avoid syntax conflicts one avoids attaching special meaning to any character that has special meaning in the underlying OS languages of interest. -- Richard Harter, Software Maintenance and Development Systems, Inc. Net address: jjmhome!smds!rh Phone: 508-369-7398 US Mail: SMDS Inc., PO Box 555, Concord MA 01742 This sentence no verb. This sentence short. This signature done.