From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: sending function arguments to recursive function calls
Date: Mon, 20 May 2013 21:55:14 +0200 [thread overview]
Message-ID: <87d2slmnod.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: mailman.94.1369078320.22516.help-gnu-emacs@gnu.org
Dmitry Gutov <dgutov@yandex.ru> writes:
> During the few years I've been using Emacs, I think I've only used the
> ability to change the value of a parameter in a caller function once,
> deep inside the Helm codebase. Sure enough, in a few months, the caller
> function code has changed, and my function broke.
Definitely.
But then any kind of patching is doomed, if not integrated in the
upstream.
--
__Pascal Bourguignon__ http://www.informatimago.com/
A bad day in () is better than a good day in {}.
You can take the lisper out of the lisp job, but you can't take the lisp out
of the lisper (; -- antifuchs
next prev parent reply other threads:[~2013-05-20 19:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 13:01 sending function arguments to recursive function calls Gauthier Östervall
2013-05-04 15:30 ` Drew Adams
2013-05-07 11:25 ` Gauthier Östervall
2013-05-07 14:04 ` Drew Adams
2013-05-08 12:21 ` Stefan Monnier
2013-05-09 8:35 ` Gauthier Östervall
2013-05-09 12:23 ` Stefan Monnier
2013-05-12 13:19 ` Gauthier Östervall
2013-05-13 14:55 ` Stefan Monnier
2013-05-17 12:20 ` Gauthier Östervall
2013-05-17 12:26 ` Dmitry Gutov
2013-05-17 14:31 ` Drew Adams
2013-05-19 16:57 ` Dmitry Gutov
2013-05-21 16:34 ` Drew Adams
[not found] ` <mailman.70.1368982677.22516.help-gnu-emacs@gnu.org>
2013-05-19 20:59 ` Pascal J. Bourguignon
2013-05-20 19:31 ` Dmitry Gutov
[not found] ` <mailman.94.1369078320.22516.help-gnu-emacs@gnu.org>
2013-05-20 19:55 ` Pascal J. Bourguignon [this message]
2013-05-07 14:32 ` Pascal J. Bourguignon
[not found] ` <mailman.25279.1367935468.855.help-gnu-emacs@gnu.org>
2013-05-07 14:55 ` Pascal J. Bourguignon
2013-05-08 12:25 ` Stefan Monnier
2013-05-05 1:22 ` Stefan Monnier
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=87d2slmnod.fsf@kuiper.lan.informatimago.com \
--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.
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).