From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Pascal J. Bourguignon" Newsgroups: gmane.emacs.help Subject: Re: sending function arguments to recursive function calls Date: Mon, 20 May 2013 21:55:14 +0200 Organization: Informatimago Message-ID: <87d2slmnod.fsf@kuiper.lan.informatimago.com> References: <0F54256BD7B94384AC4DDA919D502C20@us.oracle.com> <4D1DF48A7223443FA454C07B20B80E21@us.oracle.com> <87mwrt7py6.fsf@yandex.ru> <2AC6E6871319483CABA0387DEF8B39CC@us.oracle.com> <878v3aofcy.fsf@kuiper.lan.informatimago.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1369080297 26885 80.91.229.3 (20 May 2013 20:04:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 20 May 2013 20:04:57 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon May 20 22:04:57 2013 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 1UeWKF-0005uC-8g for geh-help-gnu-emacs@m.gmane.org; Mon, 20 May 2013 22:04:55 +0200 Original-Received: from localhost ([::1]:49253 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UeWKE-000471-Pj for geh-help-gnu-emacs@m.gmane.org; Mon, 20 May 2013 16:04:54 -0400 Original-Path: usenet.stanford.edu!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 18 Original-X-Trace: individual.net gSesc+0Sp+vB5KPkMUJGqQWkT56d/d11yRCA1v/PIx2zuiz4PI Cancel-Lock: sha1:ZjFiM2VkMjI4MWY4ZTRiMDU2N2EyY2IxY2RkNGJmMGJhZWE1MzI1NQ== sha1:kxbQKOUT8ItBfBt7tb9fba/7OX4= Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEUAAAD///+l2Z/dAAAA oElEQVR4nK3OsRHCMAwF0O8YQufUNIQRGIAja9CxSA55AxZgFO4coMgYrEDDQZWPIlNAjwq9 033pbOBPtbXuB6PKNBn5gZkhGa86Z4x2wE67O+06WxGD/HCOGR0deY3f9Ijwwt7rNGNf6Oac l/GuZTF1wFGKiYYHKSFAkjIo1b6sCYS1sVmFhhhahKQssRjRT90ITWUk6vvK3RsPGs+M1RuR mV+hO/VvFAAAAABJRU5ErkJggg== X-Accept-Language: fr, es, en User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Original-Xref: usenet.stanford.edu gnu.emacs.help:198661 X-Mailman-Approved-At: Mon, 20 May 2013 16:04:45 -0400 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:90926 Archived-At: Dmitry Gutov 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