unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jérôme Marant" <jmarant@free.fr>
Cc: emacs-devel@gnu.org
Subject: Re: Extending GUD tooltips
Date: Thu, 28 Apr 2005 11:05:53 +0200	[thread overview]
Message-ID: <1114679153.4270a77122b20@imp6-q.free.fr> (raw)
In-Reply-To: <17008.6540.383765.100951@farnswood.snap.net.nz>

Quoting Nick Roberts <nickrob@snap.net.nz>:

>  > Btw, I have a question not directly related to your patch: why do you
>  > absolutely need to put gud-specific code within tooltip.el?
>
> Well, I didn't put them there, but it certainly makes coding easier because
> GUD tooltips use a lot of the generic code.

You mean you did put them there I guess or I misunderstood the first
part of your sentence.

>  > IMHO, tooltip.el shall only provide some generic code that can be used
>  > by other modes, externaly. AFAIK, this what other modes do.
>
> Maybe thats a general rule but one needs to be quantitative. tooltip.el is
> about 500 lines and about half that code is for GUD. So maybe 250 lines get
> loaded in Emacs through loadup.el but I'm not sure that it amounts to much in

I think it is a general rule of software design (I don't pretend to give
software design lessons though).

Are other modes likely to use those gud tooltip functions? If not,
they should not be put in the same module.

How id GUD different from other modes in this respect?

> memory. On the other hand, gud.el is about 3000 lines, so moving GUD tooltips
> there would make the file over ten times larger than tooltip.el. Can you see
> any practical benefit in doing this?

I fail to understand the problem from the the gud POV.
gud-specific tooltip code would only be loaded for anyone using gud anyway,
right?

Cheers,

--
Jérôme Marant

  reply	other threads:[~2005-04-28  9:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27  3:47 Extending GUD tooltips Nick Roberts
2005-04-27  6:46 ` Jérôme Marant
2005-04-27 23:00   ` Nick Roberts
2005-04-28  9:05     ` Jérôme Marant [this message]
2005-04-29  0:13     ` Richard Stallman
2005-05-03 10:45       ` Nick Roberts
     [not found]         ` <20050503233230.B47179F50F@mirror.positive-internet.com>
2005-05-04 16:57           ` Jérôme Marant
2005-05-05 19:45             ` Richard Stallman
2005-05-05 23:45           ` Nick Roberts
2005-05-06 18:51             ` Richard Stallman
2005-05-07  0:28               ` Nick Roberts
2005-05-07 18:35                 ` Richard Stallman
2005-05-10 20:25             ` Jérôme Marant
2005-04-27 18:36 ` Richard Stallman

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=1114679153.4270a77122b20@imp6-q.free.fr \
    --to=jmarant@free.fr \
    --cc=emacs-devel@gnu.org \
    --cc=jerome.marant@free.fr \
    /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).