From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "scopeview ." Newsgroups: gmane.emacs.devel Subject: Re: What's the best way to write complex emacs extension Date: Tue, 4 Nov 2014 08:16:13 +0800 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c3ac1efca6990506fd5e83 X-Trace: ger.gmane.org 1415067169 5319 80.91.229.3 (4 Nov 2014 02:12:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 4 Nov 2014 02:12:49 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 04 03:12:42 2014 Return-path: Envelope-to: ged-emacs-devel@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 1XlTbu-0006dp-7V for ged-emacs-devel@m.gmane.org; Tue, 04 Nov 2014 03:12:42 +0100 Original-Received: from localhost ([::1]:38169 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XlTbt-0002Q0-P4 for ged-emacs-devel@m.gmane.org; Mon, 03 Nov 2014 21:12:41 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37010) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XlRnH-00084W-46 for emacs-devel@gnu.org; Mon, 03 Nov 2014 19:16:20 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XlRnC-00007M-Ha for emacs-devel@gnu.org; Mon, 03 Nov 2014 19:16:19 -0500 Original-Received: from mail-qa0-x232.google.com ([2607:f8b0:400d:c00::232]:62209) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XlRnC-00007G-Bm for emacs-devel@gnu.org; Mon, 03 Nov 2014 19:16:14 -0500 Original-Received: by mail-qa0-f50.google.com with SMTP id bm13so7295090qab.23 for ; Mon, 03 Nov 2014 16:16:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IL57+Rk3XiHemAPzExqNJ0Z0Qz61uIPqtpeLEMEXs7s=; b=TUxPC2tPjhmsMPYfTYosQoSAe6DIPzmpzQxOnUbCNjas+7NdTFhY9Qt/5OOxmnb9De fOFAeo7xrErNwXlHl390zaMUIQ4vYPyuqRTNqFHKJ45+w3rWT4386T7nZDCHj9/vM8YR DdItb9+yoe/5dJP8sSQCbZbbnU4eV9qP6d5OoUdYgCm3HpLxEFbWlxU7gJutvOxMK8mk Rv3eJayHUCkpUYIXwG4vPGzyYHZEQjhn1syd79LqrF2wWGqvyjr6B029Jzo3w2mxqLYg +AbwyWkOwSXFVcL644RUAmkK9GqFG1ISHDDqbgAtxDKASmTqmxpYKb/H4vwxCjIOGkoy WyVg== X-Received: by 10.224.124.67 with SMTP id t3mr70160022qar.20.1415060173659; Mon, 03 Nov 2014 16:16:13 -0800 (PST) Original-Received: by 10.96.79.193 with HTTP; Mon, 3 Nov 2014 16:16:13 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400d:c00::232 X-Mailman-Approved-At: Mon, 03 Nov 2014 21:12:19 -0500 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:176329 Archived-At: --001a11c3ac1efca6990506fd5e83 Content-Type: text/plain; charset=UTF-8 Thanks I have used edebug for developing my elisp extension. I just feel elisp + XML + c binary for complex extension is not so convenient. Even with edebug, when some predication failed, I should guess where it could be then set edebug function entry. On Sun, Nov 2, 2014 at 1:27 PM, Stefan Monnier wrote: > > When I wrote my simple extension, pure elisp code is ok. But I found it > is > > hard to write complex elisp extension. Because when elisp predication > > failed (for example stringp) it hard to find out the failed predication > > place. (no file:function:line_number or backtrace) > > Options => Enter Debugger on Error > > > Stefan > --001a11c3ac1efca6990506fd5e83 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks

I have used edebug for devel= oping my elisp extension.

I just feel elisp + XML + c binary f= or complex extension is not so convenient. Even with edebug, when some pred= ication failed, I should guess where it could be then set edebug function e= ntry.

On= Sun, Nov 2, 2014 at 1:27 PM, Stefan Monnier <monnier@iro.umontrea= l.ca> wrote:
> When I wrote my simple extension, pure elisp code is ok. But I foun= d it is
> hard to write complex elisp extension. Because when elisp predication<= br> > failed (for example stringp) it hard to find out the failed predicatio= n
> place. (no file:function:line_number or backtrace)

Options =3D> Enter Debugger on Error


=C2=A0 =C2=A0 =C2=A0 =C2=A0 Stefan

--001a11c3ac1efca6990506fd5e83--