unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Stefan Monnier <foo@acm.com>" <monnier+gnu.emacs.help/news/@flint.cs.yale.edu>
Subject: Re: reading the C source of Emacs
Date: 12 Jan 2003 15:59:39 -0500	[thread overview]
Message-ID: <5l3cnydqys.fsf@rum.cs.yale.edu> (raw)
In-Reply-To: uznq74o1c.fsf@ID-87814.user.dfncis.de

> Not surprisingly I am pretty lost. What is a good starting point to
> read those sources? Is there any recommended order of reading?

In my experience, the best way to start understanding a (large) piece of
code, is to look at a small part of it that you expect you should be able
to more or less understand, and once you feel like you understand it
somewhat, change it in an apparently innocuous way.

Most likely it will wreak havoc because you actually completely missed
several important aspects of what the code does, but by looking at how it
breaks, you'll get to understand those things you missed.

Having knowledgeable people at hand makes the experience less
painful, of course.


        Stefan

  parent reply	other threads:[~2003-01-12 20:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-11 17:03 reading the C source of Emacs Oliver Scholz
2003-01-11 17:43 ` David Kastrup
2003-01-12 16:31   ` Oliver Scholz
2003-01-11 21:26 ` Kai Großjohann
2003-01-12 16:37   ` Oliver Scholz
2003-01-12 19:56     ` Kai Großjohann
2003-01-12 21:45       ` Oliver Scholz
2003-01-12 22:16         ` David Kastrup
2003-01-12 20:59 ` Stefan Monnier <foo@acm.com> [this message]
2003-01-17  4:55   ` Oliver Scholz
2003-01-17 11:41     ` David Kastrup
2003-01-17 17:09     ` Kai Großjohann
2003-01-13  5:52 ` Janusz S. Bień
     [not found] ` <mailman.202.1042437305.21513.help-gnu-emacs@gnu.org>
2003-01-13  6:17   ` Miles Bader

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=5l3cnydqys.fsf@rum.cs.yale.edu \
    --to=monnier+gnu.emacs.help/news/@flint.cs.yale.edu \
    /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).