From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: PJ Weisberg Newsgroups: gmane.emacs.help Subject: Re: Style Issues in Lisp and Scheme programming, setq versus let ... and onion structure with multiple cores or eyes or kernels Re: string to list or string to array Date: Mon, 22 Oct 2012 19:36:15 -0700 Message-ID: References: <62642868-f757-4115-a047-34c319a1c30f@o5g2000yqi.googlegroups.com> <87pq4c848a.fsf@kuiper.lan.informatimago.com> <4e87f58c-72fc-457b-8596-c792c39472e5@m4g2000yqb.googlegroups.com> <87zk3f7ey7.fsf@kuiper.lan.informatimago.com> <657d823b-990f-4a2b-a57c-2c644099ddcd@z2g2000yqj.googlegroups.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: ger.gmane.org 1350959787 31117 80.91.229.3 (23 Oct 2012 02:36:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 23 Oct 2012 02:36:27 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: Swami Tota Ram Shankar Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Oct 23 04:36:35 2012 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TQUM4-0008Dt-D9 for geh-help-gnu-emacs@m.gmane.org; Tue, 23 Oct 2012 04:36:32 +0200 Original-Received: from localhost ([::1]:42848 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TQULw-0007Wp-On for geh-help-gnu-emacs@m.gmane.org; Mon, 22 Oct 2012 22:36:24 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:42431) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TQULq-0007WZ-VX for help-gnu-emacs@gnu.org; Mon, 22 Oct 2012 22:36:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TQULp-0006cw-A0 for help-gnu-emacs@gnu.org; Mon, 22 Oct 2012 22:36:18 -0400 Original-Received: from mail-lb0-f169.google.com ([209.85.217.169]:47778) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TQULp-0006ca-2R for help-gnu-emacs@gnu.org; Mon, 22 Oct 2012 22:36:17 -0400 Original-Received: by mail-lb0-f169.google.com with SMTP id k6so66496lbo.0 for ; Mon, 22 Oct 2012 19:36:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=I8wJgDzJM75190tbic2b7sxbam7foVx0lqR7lhGfosQ=; b=viL6nVyyHORWG5/nlDzmcht2OgAjkyeWdAXV330T6dShwxOxP8U9eDaH047Viy0aF9 ieFit2gLmC8JTibbcYNPRzUWa8jmgeQJvOIFfbc/1nRpSpHdE5LBn+jmiODTID3U0dPu r4A7fpM/I2R1mBFzqU1joM9uAc09jqVnNl5qVgWFPla43f0JwBmIaq/RWHW6pDQ9VuLk qR3XkwngGPWSuO5l9/KEHA6E6kbmcQYioESMk4yzdVEXf2r9oUV4PFKpI4VmacQiln3Y 55JFBJ1gfpG4GZkAlfr8wX+usQWD7j/2KDu8zDwCJ7KpiJj5zl/ghoCRmS4MrWgS75EX wtBg== Original-Received: by 10.152.105.103 with SMTP id gl7mr9791541lab.10.1350959775430; Mon, 22 Oct 2012 19:36:15 -0700 (PDT) Original-Received: by 10.112.6.197 with HTTP; Mon, 22 Oct 2012 19:36:15 -0700 (PDT) In-Reply-To: <657d823b-990f-4a2b-a57c-2c644099ddcd@z2g2000yqj.googlegroups.com> X-Google-Sender-Auth: yZnP5BiYJU9o9cbFF5fzMYsnISA X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.217.169 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:87373 Archived-At: On Mon, Oct 22, 2012 at 6:16 PM, Swami Tota Ram Shankar wrote: > For example, the imperative programming style, flows nicely from top > to bottom. The eye has to move L->R and top to bottom to understand > the screenful module, as in C. > > I have found that let, and functional style leads to an onion type > structure. > > f(g(h(x,y),z,k(alpha,beta,l(theta)))w) That could be valid C code, but it's probably not Lisp code, unless you really do have a function named "x,y". > If it is short, its not an issue, but the multiple cores or eyes of > the onion, makes it impossible to grasp the structure. Just one small tip: when reading lisp code, pay more attention to the indentation then to the parentheses. Of course the compiler/interpreter doesn't pay attention to the indentation, but the author probably did. -PJ Gehm's Corollary to Clark's Law: Any technology distinguishable from magic is insufficiently advanced.