From: "Eli Zaretskii" <eliz@elta.co.il>
Subject: Re: what is the point of point-min?
Date: Fri, 29 Aug 2003 13:30:51 +0200 [thread overview]
Message-ID: <7458-Fri29Aug2003133050+0300-eliz@elta.co.il> (raw)
In-Reply-To: <p04310102bb741930112b@[198.17.100.22]> (message from Greg Hill on Thu, 28 Aug 2003 14:11:30 -0700)
> Date: Thu, 28 Aug 2003 14:11:30 -0700
> From: Greg Hill <ghill@synergymicro.com>
>
> Though not by any means a "C guru," I
> have done a fair amount of both writing C code from scratch and
> maintaining other people's C code; and I have long-since concluded
> that looking at the C source for Emacs hoping to figure out what it
> is doing is a total waste of my time. I have never made any
> significant progress in anything close to a reasonable amount of time.
What other programs of comparable size did you have to read and
understand? Perhaps Emacs (more than 300K lines of C) is much larger
than you are used to?
FWIW, the macros are there to make reading code _easier_, not harder.
Macros such as CONSP, STRINGP, XCONS, etc., should be almost instantly
understandable to anyone who knows a bit of Lisp. By contrast, if
you'd see something like
if ((enum Lisp_type) foo.u.type == Lisp_Cons)
you might have hard time understanding what is going on.
(It is true that, if you need to _debug_ some Emacs code, you need to
actually read and understand the macros involved. But the need to
debug the C code is not the issue in this thread, is it?)
next prev parent reply other threads:[~2003-08-29 11:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E19s71c-0005cn-KT@monty-python.gnu.org>
2003-08-27 23:40 ` what is the point of point-min? Joe Corneli
[not found] ` <mailman.1156.1062027752.29551.help-gnu-emacs@gnu.org>
2003-08-28 0:23 ` Jesper Harder
2003-08-28 16:17 ` Kevin Rodgers
2003-08-28 17:05 ` Jesper Harder
2003-08-28 17:59 ` Barry Margolin
2003-08-28 18:47 ` Jesper Harder
2003-08-28 20:05 ` Kai Großjohann
2003-08-28 21:11 ` Greg Hill
2003-08-29 11:30 ` Eli Zaretskii [this message]
2003-08-28 22:11 ` Johan Bockgård
[not found] ` <mailman.1207.1062105211.29551.help-gnu-emacs@gnu.org>
2003-08-29 7:21 ` Oliver Scholz
2003-08-29 11:32 ` Eli Zaretskii
2003-08-29 10:41 ` Kai Großjohann
2003-08-29 7:33 ` Oliver Scholz
2003-08-29 12:44 ` Rob Thorpe
2003-08-30 2:54 ` Jesper Harder
2003-09-01 13:41 ` Rob Thorpe
2003-09-07 6:50 ` Jim Janney
2003-09-07 17:28 ` Eli Zaretskii
2003-08-28 18:34 ` Kevin Rodgers
[not found] ` <m3znhttxic.fsf@peorth.gweep.net>
2003-08-28 20:39 ` Jesper Harder
[not found] ` <m31xv431u6.fsf@peorth.gweep.net>
2003-08-30 3:32 ` Jesper Harder
[not found] ` <m3ekz2idao.fsf@peorth.gweep.net>
2003-08-31 10:58 ` Unknown
2003-09-01 17:04 ` 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=7458-Fri29Aug2003133050+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
/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).