From: "Eric M. Ludlam" <eric@siege-engine.com>
To: rms@gnu.org
Cc: jasonr@gnu.org, lennart.borgman@gmail.com, sdl.web@gmail.com,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re[2]: Multiple major modes
Date: Sun, 8 Jul 2007 20:49:41 -0400 [thread overview]
Message-ID: <200707090049.l690nf6e027141@projectile.siege-engine.com> (raw)
In-Reply-To: <E1I7fAT-0001WO-JY@fencepost.gnu.org> (message from Richard Stallman on Sun, 08 Jul 2007 18:23:49 -0400)
>>> Richard Stallman <rms@gnu.org> seems to think that:
> The use syntax of an overloadable function is similar to programs that
> call `indent-for-tab-command', or `indent-according-to-mode', but
> there is no restriction forcing `according-to-mode' as part of the
> function name.
>
>I understand the similarity, but I see the difference too.
>The source code of `indent-according-to-mode' shows that it
>calls something that can be set differently by different modes.
>
>That's why I prefer using a variable.
>
>However, you didn't show precisely what this feature looks like.
>Perhaps I got the wrong idea of the feature. Can you show me
>what it looks like?
Hi,
Here is a use case from semantic, my parsing tool. This is a
function that would take a name as found in sources, and split it so
that namespaces (if any) and the name are returned. In many
languages there is nothing special to do, but in C++, it needs to do
something special. Instead of putting c++ code in the first file, it
is instead placed in a C specific file that contains many C specific
differences. Of course, the doc string talks about C++, but only as
an example.
I picked this case because it's very short.
semantic-analyze.el:
--------------------
(define-overload semantic-analyze-split-name (name)
"Split a tag NAME into a sequence.
Sometimes NAMES are gathered from the parser that are compounded,
such as in C++ where foo::bar means:
\"The class BAR in the namespace FOO.\"
Return the string NAME for no change, or a list if it needs to be split.")
(defun semantic-analyze-split-name-default (name)
"Don't split up NAME by default."
name)
--------------------
As you can see, there is no implementation at the initial
declaration. In this example, the `-default' is a separate function,
because a body could be given to the original that would wrap either
the `-default' of a mode specific implementation.
semantic-c.el:
--------------
(define-mode-local-override semantic-analyze-split-name c-mode (name)
"Split up tag names on colon (:) boundaries."
(let ((ans (split-string name ":")))
(if (= (length ans) 1)
name
(delete "" ans))))
--------------
If you use "C-h f semantic-analyze-split-name RET" you get:
---------------
semantic-analyze-split-name is a compiled Lisp function in `semantic-analyze.el'.
(semantic-analyze-split-name name)
This function can be overloaded (see `define-mode-local-override' for details).
Split a tag name into a sequence.
Sometimes NAMES are gathered from the parser that are compounded,
such as in C++ where foo::bar means:
"The class BAR in the namespace FOO."
Return the string name for no change, or a list if it needs to be split.
[back]
---------------
which would be improved if the doc for individual overloads could be
specified, though I haven't done that yet. Doing so would make it
much easier to find the implementation actually being run in a
particular case.
I hope this helps.
Eric
--
Eric Ludlam: zappo@gnu.org, eric@siege-engine.com
Home: http://www.ludlam.net Siege: www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: www.gnu.org
next prev parent reply other threads:[~2007-07-09 0:49 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 23:27 Should nXML be included Leo
2007-06-12 10:50 ` Lennart Borgman (gmail)
2007-06-12 11:21 ` Jason Rumney
2007-06-12 12:57 ` Lennart Borgman (gmail)
2007-06-12 13:42 ` Peter Heslin
2007-06-12 14:20 ` Jason Rumney
2007-06-12 15:06 ` Multiple major modes (was: Should nXML be included) Stefan Monnier
2007-06-12 15:15 ` Multiple major modes Leo
2007-06-12 18:48 ` Lennart Borgman (gmail)
2007-06-12 20:14 ` Re[2]: " Eric M. Ludlam
2007-06-12 21:04 ` Lennart Borgman (gmail)
2007-06-12 23:10 ` Stefan Monnier
2007-06-13 16:22 ` Richard Stallman
2007-06-13 16:22 ` Richard Stallman
2007-06-19 2:09 ` Re[2]: " Eric M. Ludlam
2007-06-24 14:41 ` Richard Stallman
2007-06-25 14:04 ` Re[2]: " Eric M. Ludlam
2007-07-01 20:40 ` Richard Stallman
2007-07-05 2:29 ` Re[2]: " Eric M. Ludlam
2007-07-05 20:34 ` Richard Stallman
2007-07-01 20:40 ` Richard Stallman
2007-07-04 16:35 ` T. V. Raman
2007-07-04 17:01 ` David Kastrup
2007-07-05 1:31 ` Richard Stallman
2007-07-05 14:49 ` Stefan Monnier
2007-07-06 4:38 ` Richard Stallman
2007-07-06 6:01 ` Stephen J. Turnbull
2007-07-07 13:07 ` Richard Stallman
2007-07-07 14:13 ` Lennart Borgman (gmail)
2007-07-08 16:56 ` Richard Stallman
2007-09-04 9:03 ` Highlight advice (was: Multiple major modes) Johan Bockgård
2007-07-07 17:43 ` Multiple major modes Stephen J. Turnbull
2007-07-06 16:00 ` Stefan Monnier
2007-07-06 16:10 ` Drew Adams
2007-07-07 13:06 ` Richard Stallman
2007-07-07 17:21 ` Stephen J. Turnbull
2007-07-08 16:55 ` Richard Stallman
2007-07-09 5:29 ` Stephen J. Turnbull
2007-07-09 17:21 ` Richard Stallman
2007-07-07 0:48 ` Johan Bockgård
2007-07-05 1:44 ` Re[2]: " Eric M. Ludlam
2007-07-08 22:23 ` Richard Stallman
2007-07-09 0:49 ` Eric M. Ludlam [this message]
2007-07-09 17:21 ` Richard Stallman
2007-06-12 13:26 ` Should nXML be included Stefan Monnier
2007-06-12 13:16 ` Peter Heslin
2007-06-12 13:11 ` Leo
2007-06-12 13:59 ` joakim
2007-06-12 14:17 ` Peter Heslin
2007-06-12 14:14 ` David Kastrup
2007-06-12 15:11 ` Stefan Monnier
2007-06-13 8:06 ` Richard Stallman
2007-06-13 17:45 ` Claus
2007-06-14 16:19 ` Richard Stallman
2007-06-14 16:28 ` Leo
2007-06-15 19:21 ` Richard Stallman
2007-06-14 17:44 ` Eric Hanchrow
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=200707090049.l690nf6e027141@projectile.siege-engine.com \
--to=eric@siege-engine.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
--cc=sdl.web@gmail.com \
/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.