unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Testing errors from macros with ERT and byte-compilation
Date: Sun, 18 Aug 2013 14:55:31 -0400	[thread overview]
Message-ID: <q0fvu63k2k.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87zjsfnu6k.fsf@engster.org> (David Engster's message of "Sun, 18 Aug 2013 12:56:51 +0200")

David Engster wrote:

> Or should I just use 'no-byte-compile: t' for the test suite?

It would seem overkill to do that for the entire test-suite.
Why not just separate out the things that don't compile into separate
file(s) and mark those no-byte-compile?
How does it work now?

Or use something like:

(ert-deftest eieio-broken-initform ()
  (should-error
    (eval '(defclass broken-init nil
         ((broken :initform 1
                        :type string))
                             "This class should break.")
                               :type 'invalid-slot-type)))

I feel I don't really understand what the problem is (I'm saying that a
lot today, maybe it's me...).



  reply	other threads:[~2013-08-18 18:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-18 10:56 Testing errors from macros with ERT and byte-compilation David Engster
2013-08-18 18:55 ` Glenn Morris [this message]
2013-08-18 19:13   ` David Engster

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=q0fvu63k2k.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@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).