Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Gregory Ewing Newsgroups: comp.lang.python Subject: Re: Lisp refactoring puzzle Date: Thu, 14 Jul 2011 15:12:41 +1200 Lines: 13 Message-ID: <98755cFolU1@mid.individual.net> References: <19f8eb5b-cc90-472a-8399-4a5787b6fecf@glegroupsg2000goo.googlegroups.com> <2c59f63a-b46f-4ea9-bc12-da4841687117@l28g2000yqc.googlegroups.com> <5cb297e4-6a39-461c-98c5-639e72e166af@p10g2000prf.googlegroups.com> <87mxgilh15.fsf@mithlond.arda> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net ZKM6tTTNRs/l9uNgf1Y8Ug7dco29wkGu7MPS17EY/7QKaYdBlR Cancel-Lock: sha1:j4T4mIYE/DFDRplIej5QkHZj7Oo= User-Agent: Mozilla Thunderbird 1.0.5 (Macintosh/20050711) X-Accept-Language: en-us, en In-Reply-To: <87mxgilh15.fsf@mithlond.arda> Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:9457 Teemu Likonen wrote: > Please don't forget that the whole point of Lisps' (f x) syntax is that > code is also Lisp data. It's possible to design other syntaxes that have a similar property. Prolog, for example -- a Prolog program is expressed in terms of Prolog data structures, yet it manages to have things that look like fairly normal function calls and infix expressions. -- Greg