unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Carsten Mattner <carstenmattner@googlemail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: gdb scripting language (was OSX crash)
Date: Mon, 19 Dec 2011 22:04:18 +0900	[thread overview]
Message-ID: <87ty4wk90t.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <CACY+Hvpjg=Ke0ovSk26KufrSg+dm6DP7h3D-H1W==qHhxuzKuw@mail.gmail.com>

Carsten Mattner writes:

 > [Python is] only made popular due to being the new Perl of the
 > Linux distros.

I'm not sure exactly what your sentence referred to, but if the edit
above it correctly reflects your intent, your statement is false.
There are excellent reasons why Python is the scripting language
chosen by most distros that have made such a choice recently.  Those
reasons don't necessarily apply to an extension language, of course,
and we should be careful about that distinction.  However, I do find
some of the features of Python such as iterators, comprehensions, and
occasionally even generators to be useful at the interpreter prompt,
so I suspect they would be similarly useful if Python were used as an
extension language.

Of course the other scripting languages you mention are of similar
power, but I don't find them any easier to learn than I found Python
(and I've learned several languages since I learned Python; I should
be better at it now!)  There's an advantage to having one language
popular enough that you only need to learn that one, which gives
Python a substantial edge on the others (except Perl, of course).

It's also true that I find them all harder to learn than I found
forgetting Perl, but that, of course, is praising with faint damns.

 > Python being in lldb is one of problems FreeBSD faces with putting
 > LLDB in the base system.

If you say so, I'll take your word for it.  Nevertheless, Lisps face
far more resistance from the average member of the free software
community and the broader (or if you prefer, "neighboring") open
source community.

This *is* a problem for Emacs, and I think Lispers (and advocates of
functional languages in general) could learn a lot from the success of
Python.



  reply	other threads:[~2011-12-19 13:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-19 12:12 gdb scripting language (was OSX crash) Carsten Mattner
2011-12-19 13:04 ` Stephen J. Turnbull [this message]
2011-12-19 13:25   ` Carsten Mattner
2011-12-19 14:27     ` Stephen J. Turnbull
2011-12-19 14:50       ` Carsten Mattner
2011-12-19 20:47         ` Richard Stallman
2011-12-19 20:50           ` Carsten Mattner
2011-12-19 21:10           ` Carsten Mattner
2011-12-21 13:56             ` gdb scripting language Andy Wingo

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87ty4wk90t.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=carstenmattner@googlemail.com \
    --cc=emacs-devel@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).