Re: How to improve the readability of (any) LISP or any highlevel functional language to the level of FORTH ?

Article View: comp.lang.functional

Article #1144

Back to comp.lang.functional Previous Next

#1144

From: Jan Burse
Date: Fri, 21 Jan 2011 16:15

57 lines
3349 bytes

I am voting for RPL:
http://en.wikipedia.org/wiki/RPL_(programming_language)

m_l_g3 schrieb:
> On Jan 1, 10:04 am, girosenth<girose...@india.com>  wrote:
>> How to improve the readability of (any) LISP or any highlevel
>> functional language to the level of FORTH ?
>
> ...
>>
>> How do you make it readable ?
> ...
>>
>> (f (g (h (j (k (l ops)))...)))
>
> (e
>     (f
>        (g (h i)
>           (j k l)
>        )
>        (m (n o (p q))
>           (r (s t) u)
> )  )  )
>
> The rule: if you don't see the closing paren moving the eyes down,
> it's on the right.
> But it either to the right or down, no other option.
>
> Since closing parens are visually identical, there's no need to one
> line per paren;
> this is shown at the last line (yes, their visual and logical
> orderings are different,
> but they are identical parens otherwise worth only counting!).
>
>
>
>> Is there a postfix functional language that also gets rid of parens
>> and is not as primitive as FORTH or POSTSCRIPT ?
>
> There is a prefix/infix one: Haskell with its ($) and (.) operators
> and... well... monads.
>
> As to Forth, you may try to layout control structures on the right,
> as if RPN is not enough:
>
> : MAX   2dup>       if
>              drop    else
>              nip     then
> ;
>
> : foo
>    10 0               do
>       i 3 mod 0= if
>          i .     then loop
> ;
>
>

Technical Details

Message-ID: <ihcbfo$ngc$2@news.albasani.net>

Path:

arc1-ca.pugleaf.net!g2news2.google.com!news3.google.com!feeder.news-service.com!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!news.wiretrip.org!news2.arglkargh.de!news.albasani.net!not-for-mail

References:

<80ceeca0-1d32-47d1-ba96-feb4d9729c3a@v17g2000yqv.googlegroups.com> <5121f8b1-a8d2-4587-a45e-387469762668@m13g2000yqb.googlegroups.com>

Show Full Headers

Complete Article Headers

X-Google-Thread: 107f24,1641de092071599d
X-Google-NewGroupId: yes
X-Google-Thread: f4fd2,1641de092071599d
X-Google-NewGroupId: yes
X-Google-Thread: 103b8b,1641de092071599d
X-Google-NewGroupId: yes
X-Google-Thread: fd7c9,1641de092071599d
X-Google-NewGroupId: yes
X-Google-Attributes: gid4e63bbc566,gidf85ca024c1,gid39ae015015,gid2832dde05d,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news2.google.com!news3.google.com!feeder.news-service.com!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!news.wiretrip.org!news2.arglkargh.de!news.albasani.net!not-for-mail
From: Jan Burse <janburse@fastmail.fm>
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: Fri, 21 Jan 2011 17:15:52 +0100
Organization: albasani.net
Lines: 58
Message-ID: <ihcbfo$ngc$2@news.albasani.net>
References: <80ceeca0-1d32-47d1-ba96-feb4d9729c3a@v17g2000yqv.googlegroups.com> <5121f8b1-a8d2-4587-a45e-387469762668@m13g2000yqb.googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: news.albasani.net sqJ7ZHIDbv6j687LqD16NWBXeiWTzYuA31BTii9eYkfxbJYAQtSyY2KWjywa7cOiEjexWpM/HOMf16cafkqDe3C/iRoLyVJCRzykK3uV63BSNCxpgxIUPyrFdGpgJltD
NNTP-Posting-Date: Fri, 21 Jan 2011 16:15:52 +0000 (UTC)
In-Reply-To: <5121f8b1-a8d2-4587-a45e-387469762668@m13g2000yqb.googlegroups.com>
Cancel-Lock: sha1:SKeu7SNq1pbi0lCNMDiH+XWrSf4=
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11
Injection-Info: news.albasani.net; logging-data="/jF3ikBqMvS9uhvu/Kp0dRBv+vSXdtZmZ7B8WlPklXzYlaTYaQPYz4TKrNYWQ5vK6YJA8oYflKt+jkprmbRTLExKkOqnL/44CHs6nP8WAPXyL6huMRiUWVXPnKUh+u2k"; mail-complaints-to="abuse@albasani.net"

Reply to Parent Message