Article View: comp.lang.functional
Article #1188Re: How to improve the readability of (any) LISP or any highlevel functional language to the level of FORTH ?
From: Pascal Costanza
Date: Sat, 01 Jan 2011 23:56
Date: Sat, 01 Jan 2011 23:56
14 lines
1573 bytes
1573 bytes
On 01/01/2011 08:04, girosenth wrote: > How to improve the readability of (any) LISP or any highlevel > functional language to the level of FORTH ? I'm rather wondering how we can improve the readability of (any) English to the level of German. Pascal -- My website: http://p-cos.net Common Lisp Document Repository: http://cdr.eurolisp.org Closer to MOP & ContextL: http://common-lisp.net/project/closer/
Technical Details
Message-ID:
<8o9taaFglrU1@mid.individual.net>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news.glorb.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mailReferences:
<80ceeca0-1d32-47d1-ba96-feb4d9729c3a@v17g2000yqv.googlegroups.com>Show Full Headers
Complete Article Headers
X-Google-Thread: ee3de009bc,1641de092071599d X-Google-Attributes: gidee3de009bc,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news.glorb.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Pascal Costanza <pc@p-cos.net> Newsgroups: comp.lang.functional,comp.lang.lisp,gnu.emacs.help,comp.lang.forth,comp.lang.prolog Subject: Re: How to improve the readability of (any) LISP or any highlevel functional language to the level of FORTH ? Date: Sun, 02 Jan 2011 00:56:58 +0100 Lines: 14 Message-ID: <8o9taaFglrU1@mid.individual.net> References: <80ceeca0-1d32-47d1-ba96-feb4d9729c3a@v17g2000yqv.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net w0C8ZmixhxVgUSBIuBi6dQF6dqdaXilQgO8svkXcIlhn8gkERZ Cancel-Lock: sha1:XzywkAy00LAd2a1DS+69HclnNew= User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 In-Reply-To: <80ceeca0-1d32-47d1-ba96-feb4d9729c3a@v17g2000yqv.googlegroups.com>