emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Achim Gratz <Stromeko@NexGo.DE>
Cc: emacs-orgmode@gnu.org
Subject: Re: Build fail with emacs 24.3.1
Date: Thu, 14 Mar 2013 13:28:56 +0100	[thread overview]
Message-ID: <871ubiqi5z.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87txoete7m.fsf@bzg.ath.cx> (Bastien's message of "Thu, 14 Mar 2013 12:26:05 +0100")

Hi Achim,

Bastien <bzg@altern.org> writes:

> Yes -- but what I'm arguing about is that the special syntax is not
> needed.  Or more specifically, it is not needed to have
>
>   (org-export-define-backend html
>     ((bold . org-html-bold)
>
> instead of just
>
>   (org-export-define-backend 'html
>     '((bold . org-html-bold)

Some more thought on this.  

For `org-export-define-derived-backend', my assumption is that the
macro mimicks the style of `define-derived-mode':

(define-derived-mode CHILD PARENT NAME &optional DOCSTRING &rest BODY)

`define-derived-mode' is a macro and both CHILD and PARENT are
unquoted symbol names.

It makes sense in this case to use this syntax because those symbol
names are meant to be accessible to the user as symbols.  When I see a
(define-derived-mode CHILD...) sexp, I know I can check for the value
of CHILD, once derived-defined.

This is not the case for `org-export-define-derived-backend', where
CHILD and PARENT are not symbols the user wants to check.  There are
symbols that only have a meaning in `org-export-registered-backends',
which is what the users/devs really want to manipulate.

So mimicking `define-derived-mode' is confusing here IMHO.

Anyway, waiting for Nicolas feedback on this.

-- 
 Bastien

  reply	other threads:[~2013-03-14 12:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13  7:39 Build fail with emacs 24.3.1 Neuwirth Erich
2013-03-13 11:58 ` Bastien
2013-03-13 12:53   ` Andreas Röhler
2013-03-13 12:56     ` Bastien
2013-03-13 20:07   ` Achim Gratz
2013-03-14  2:30     ` Bastien
2013-03-14  8:26       ` Achim Gratz
2013-03-14 11:26         ` Bastien
2013-03-14 12:28           ` Bastien [this message]
2013-03-14 19:09           ` Achim Gratz
2013-03-19 17:14             ` Bastien
2013-03-20 19:03               ` `org-export-define-backend' and its friends are now defuns (was: Build fail with emacs 24.3.1) Florian Beck
2013-03-20 22:58                 ` `org-export-define-backend' and its friends are now defuns Bastien
2013-05-19 14:36               ` Build fail with emacs 24.3.1 Achim Gratz
2013-05-20 10:13                 ` Bastien
  -- strict thread matches above, loose matches on Subject: below --
2013-03-13 12:29 Susan Cragin

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.orgmode.org/

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

  git send-email \
    --in-reply-to=871ubiqi5z.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=Stromeko@NexGo.DE \
    --cc=emacs-orgmode@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/org-mode.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).