all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: schwab@suse.de, Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: gdb-ui.el assumes images support
Date: Tue, 9 Nov 2004 09:38:43 +1300	[thread overview]
Message-ID: <16783.55635.926054.394692@farnswood.snap.net.nz> (raw)
In-Reply-To: <E1CRCqz-0004jC-2y@fencepost.gnu.org>


 >     Yes, but the problem is, tooltip.el requires gdb-ui.el at compile
 >     time,
 > 
 > Can't we get rid of that dependency?
 > What is the reason for it anyway?

Yes. I don't think its needed, but gdb-ui is designed to work on text-only
terminals and presumably it won't currently when configured without X?

Anyway, tooltip.el has:

(eval-when-compile
  (require 'cl)
  (require 'comint)
  (require 'gud)
  (require 'gdb-ui))

I added the last require after Gerd Moellmann included the others. My
understanding now is that a file only requires another, at compilation,
if it uses a macro defined in that other file.

If this is the case, tooltip does not need the last three requires,
and requiring cl just seems to redefine push for compilation, so
perhaps thats not needed either.

It's sometimes hard to see why files are required at compilation, so it may
be good practice to add a comment as in vc.el:

(eval-when-compile
  (require 'cl)
  (require 'compile)
  (require 'dired)      ; for dired-map-over-marks macro
  (require 'dired-aux))	; for dired-kill-{line,tree}

I see that dired is required, but dired-kill-line, dired-kill-tree are not
macros so is dired-aux required? I think not, but if the answer is yes that
would explain the need for the requires in tooltip.

Nick

  reply	other threads:[~2004-11-08 20:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-06 17:03 gdb-ui.el assumes images support Eli Zaretskii
2004-11-07  0:23 ` Nick Roberts
2004-11-07  4:48   ` Eli Zaretskii
2004-11-07 10:35     ` Andreas Schwab
2004-11-07 22:12       ` Eli Zaretskii
2004-11-08 10:15         ` Andreas Schwab
2004-11-08 12:11           ` Eli Zaretskii
2004-11-08 16:58         ` Richard Stallman
2004-11-08 20:38           ` Nick Roberts [this message]
2004-11-08 21:23             ` Kim F. Storm
2004-11-08 22:05               ` Kevin Rodgers
2004-11-08 23:54                 ` Nick Roberts
2004-11-09  0:12                   ` Luc Teirlinck
2004-11-09  0:35                   ` Luc Teirlinck
2004-11-09  1:27                   ` Luc Teirlinck
2004-11-09 14:11                 ` Kim F. Storm
2004-11-09 17:55                   ` Kevin Rodgers
2004-11-10 16:09                     ` Richard Stallman
2004-11-09 21:29               ` Richard Stallman
2004-11-09 22:58                 ` Luc Teirlinck
2004-11-10  0:02                   ` Stefan Monnier
2004-11-10  0:08                     ` Luc Teirlinck
2004-11-11  3:14                   ` Richard Stallman
2004-11-09 23:22                 ` Kim F. Storm
2004-11-09 21:29             ` Richard Stallman
2004-11-10 11:45               ` Nick Roberts
2004-11-08 16:59     ` Richard Stallman
2004-11-09  4:28       ` Eli Zaretskii
2004-11-09 14:20         ` Kim F. Storm
2004-11-10 16:08           ` Richard Stallman
2004-11-09 21:30         ` Richard Stallman
2004-11-07 18:04 ` Richard Stallman
2004-11-08 12:47   ` Kim F. Storm
2004-11-08 14:55     ` Stefan

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16783.55635.926054.394692@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@suse.de \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.