unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Treatise on require
Date: 08 Jan 2006 06:01:13 -0500	[thread overview]
Message-ID: <jky81rhtl2.fsf@glug.org> (raw)
In-Reply-To: <28049.1136694802@olgas.newt.com>

Bill Wohler <wohler@newt.com> writes:

> feedback [...] welcome

keeping things in separate files is nice for maintenance,
but if they are meant to be used together you might want to
investigate an alternate build procedure: cat all the "core"
files together and compile that instead of each one separately.
this is the approach i take w/ EDB, which is at:

  http://www.glug.org/people/ttn/software/edb/

see file bfuncs for the concatenation (and compilation).
note that not all files are considered core, just those
that are mutually (or inextricably ;-) useful.

also, in the subdir skram/, there is machinery for collecting
information on various elements (kind of like etags i suppose)
of the EDB source.  this info can be massaged into a dependency
graph (not worth it for EDB, but you get the idea).  see file
make-skram.el and try "make skram.data" to see it in action.

of course, EDB is a separate package, so its build methods
can be as weird as necessary.  i'm not sure if this approach
would be acceptable for Emacs proper, where each file is
traditionally compiled on its own...

thi

  reply	other threads:[~2006-01-08 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08  4:33 Treatise on require Bill Wohler
2006-01-08 11:01 ` Thien-Thi Nguyen [this message]
2006-01-08 11:45 ` Andreas Schwab
2006-01-09  0:51 ` Richard M. Stallman
2006-01-09  2:20 ` 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=jky81rhtl2.fsf@glug.org \
    --to=ttn@gnu.org \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).