all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: pjb@informatimago.com (Pascal J. Bourguignon)
To: help-gnu-emacs@gnu.org
Subject: Re: Writing to buffer/file
Date: Tue, 14 Sep 2010 16:33:08 +0200	[thread overview]
Message-ID: <m2y6b49yzf.fsf@invitado-174.medicalis.es> (raw)
In-Reply-To: 87eicwfpjq.fsf@cecilia.trollope

Michael Powe <michael+gnus@trollope.org> writes:

> I sort of took this up as a challenge after reading an article the
> other day comparing perl vs elisp for text processing, in which elisp
> was given the nod as the superior language.  I could write this text
> processor pretty easily in Python.  But it would not be nearly as
> compact as what I have so far.  


Locally (ie. for a small function like yours), lisp may not be more
concise or easier to use than perl or python.   But given the ability of
lisp for abstraction (data abstraction, and functional abstraction, most
languages have it, but lisp thanks to its homoiconicity and its macro,
provides also syntactic and metalinguistic abstraction), as soon as you
have more complex processing to implement, you can better factorize
things our, and obtain a more concise and cleaner way to express your
processings.  In the mean while, you will have developed a little
library or language designed to implement your specific kind of
processing.  (Or put to use an existing library or language extension).


See for example:
http://lichteblau.blogspot.com/2009/04/xslt-10-implemented-in-common-lisp.html
http://common-lisp.net/project/xuriella/



-- 
__Pascal Bourguignon__
http://www.informatimago.com


      parent reply	other threads:[~2010-09-14 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87eicwfpjq.fsf@cecilia.trollope>
2010-09-14 14:13 ` Writing to buffer/file Pascal J. Bourguignon
2010-09-14 14:14 ` Pascal J. Bourguignon
     [not found]   ` <0388da54-19f4-4aaa-90c6-8f6262c4164f@c21g2000vba.googlegroups.com>
2010-09-14 17:46     ` Pascal J. Bourguignon
2010-09-14 14:33 ` Pascal J. Bourguignon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2y6b49yzf.fsf@invitado-174.medicalis.es \
    --to=pjb@informatimago.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.