Glad to hear the patch might be useful. Haven't signed any papers with
the FSF yet. About "plans" to submit changes and/or contribute to
CEDET/Emacs: at least i will try to fix problems by myself (if i find
any) or add features i need. Of course i would publish patches.
I'm aware about unit-tests but never used them in lisp (i'm not an
"guru" in lisp). However i use them heavy in C++. I just started on an
emacs-mode for the Boost.Test framework. At the moment it's really basic
but i've plans for it. It's available on github:
If you think that support for Boost.Test (or Qt-Test or google-test)
would be a nice feature for CEDET and have an idea where to "start"
within the CEDET stuff to support such test-frameworks let me know :-)
On 10/30/2012 11:09 PM, David Engster wrote:
> Sven Goericke writes:
>> I've attached a patch for "c.by". Also attached is an archive with
>> simple test-source and a screenshot ;-)
> Thanks! You can always try the CEDET unit and integration tests to see
> if your changes broke something. You can run them by doing 'make utest',
> 'make itest-make' and 'make itest-automake', although the latter two are
> more targeted at EDE. When changing C/C++ parsing, another good test is
> to run an integration test I added just recently; it parses some STL
> classes and hence requires an installed STL. I can be started by doing
> 'make itest-stl-batch'.
> Do you have papers signed with the FSF? Your change would qualify as a
> 'tiny change' and thus wouldn't need them, but if you plan on submitting
> further changes to CEDET and/or Emacs in the future, it can't hurt to do
> that now, since this process can take a couple of weeks.