all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Przemysław Wojnowski" <esperanto@cumego.com>
Cc: emacs-devel@gnu.org
Subject: Re: Testing library for C code
Date: Thu, 08 Oct 2015 17:44:15 +0300	[thread overview]
Message-ID: <83ziztctds.fsf@gnu.org> (raw)
In-Reply-To: <60744168ef0e5c54fe322cc55ad89f6f@mail.iq.pl>

> Date: Thu, 08 Oct 2015 13:36:30 +0200
> From: Przemysław Wojnowski <esperanto@cumego.com>
> 
> I'm looking at libraries for testing C code and I'm wondering
> if it's acceptable to use C++ to write the tests for Emacs' C code?
> 
> Simply there are more choices when C++ can be used (for example 
> googletest, cppunit).
> But if not, then there are C-only options too (for example 
> https://cmocka.org/).

In the Free Software world, the person who does the job gets to choose
the tools.  Emacs is no different.

So yes, C++ would be acceptable, IMO, as would any other tool that is
wide spread enough, if they are a good tool for the job.  The only
requirements I'd think we should insist on is (a) if a C++ compiler is
not available, the tests should be skipped without producing errors,
and (b) the tools should be free and portable.

Please note, however, that any dependency on external libraries is in
general a nuisance, however small: people need to install it.  So I
would suggest to show a few examples of tests for Emacs code using
whatever method you'd like to use, so we could see whether these
libraries indeed get us some significant advantages that justify their
use.  Making a scratch/something branch would be a good start.

Thanks.

(Btw, cppunit hints that you are looking for unit-testing frameworks,
which I'm not sure is what we want.)




  reply	other threads:[~2015-10-08 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08 11:36 Testing library for C code Przemysław Wojnowski
2015-10-08 14:44 ` Eli Zaretskii [this message]
2015-10-08 16:43   ` Przemysław Wojnowski

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=83ziztctds.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=esperanto@cumego.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.