unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: zappo@gnu.org, eric@siege-engine.com, emacs-devel@gnu.org
Subject: Re: Filename problem in CEDET merge
Date: Fri, 28 Aug 2009 11:23:55 -0400	[thread overview]
Message-ID: <87hbvsynas.fsf@stupidchicken.com> (raw)
In-Reply-To: <87ocq03ryn.fsf@stupidchicken.com> (Chong Yidong's message of "Fri, 28 Aug 2009 10:58:56 -0400")

Chong Yidong <cyd@stupidchicken.com> writes:

>>> semantic.el
>>> semantic/lex.el
>>> semantic/analyze.el
>>> semantic/analyze/debug.el
>>> semantic/analyze/fcn.el
>>> semantic/analyze/refs.el
>>>
>>> which would show up in requires as:
>>>
>>> (require 'semantic)
>>> (require 'semantic/lex)
>>> (require 'semantic/analyze)
>>> (require 'semantic/analyze/debug.el)
>>> (require 'semantic/analyze/fcn)
>>> (require 'semantic/analyze/refs)
>>
>> Ah, that's fine with me, of course.  It's similar to what I suggested,
>> but with the additional advantage of being specific in `require'.
>
> Good, then that's the approach we'll take.

One minor disadvantage of this approach, BTW, is that we'll need to
revise our byte-compilation process.  Otherwise the semantic/foo.el
files won't be byte-compiled during "make bootstrap" or "make
recompile".  But this change probably isn't difficult.




  reply	other threads:[~2009-08-28 15:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27 22:50 Filename problem in CEDET merge Chong Yidong
2009-08-28  2:26 ` Eric M. Ludlam
2009-08-28  9:45   ` Eli Zaretskii
2009-08-28 11:16     ` Eric M. Ludlam
2009-08-28 11:27       ` Miles Bader
2009-08-28 13:33       ` Eli Zaretskii
2009-08-28 13:55         ` Eric M. Ludlam
2009-08-28 14:06           ` Eli Zaretskii
2009-08-28 14:58             ` Chong Yidong
2009-08-28 15:23               ` Chong Yidong [this message]
2009-08-28 15:46                 ` Andreas Schwab
2009-08-28 15:26       ` Stefan Monnier
2009-08-28  9:42 ` Eli Zaretskii
2009-08-28 15:23   ` Stefan Monnier
2009-08-28 12:14 ` Leo
2009-08-28 13:44   ` Eli Zaretskii

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=87hbvsynas.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=eric@siege-engine.com \
    --cc=zappo@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).