[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-libmatheval] tiny texinfo patch
From: |
Aleksandar B. Samardzic |
Subject: |
Re: [Bug-libmatheval] tiny texinfo patch |
Date: |
Tue, 3 Oct 2006 23:18:26 +0200 |
User-agent: |
Mutt/1.4.2.2i |
On Tue, Oct 03, 2006 at 01:30:32PM -0400, Ed Hill wrote:
> > Thanks for problems report and for your effort in packaging
> > libmatheval for Fedora. I made some small changes in CVS, so I'd
> > appreciate if you could check it out and let me know are they OK with
> > you, so that I could release new version. The changes are as follows:
>
>
> Thanks! I'll take a look later this week or this weekend.
Incidentally, new version of Slackware is released today, so I just
installed it and it includes Guile 1.8.0; however, libmatheval is not
compiling properly using it, so there will be probably more small CVS
changes in a day or two...
> I'll take another look at your test bits since I have little
> experience writing Gnu-style test scripts and they're obviously
> useful! Speaking of which, can you perhaps recommend a starting place
> for someone who'd like to learn more about writing tests launched
> through "make check"? Are there any Gnu standards or typical patterns
> for these things or are they mostly ad-hoc?
There is a section on Autotest framework, employed by libmatheval, in
GNU autoconf manual ("info autoconf", then check section 18). As for
wrapping libmatheval C API for Guile (used in turn to write tests), I
did it by hand (this is code residing in tests/matheval.c, that you
encountered is emitting various warnings to stderr). None of these is
"obligatory" for a GNU project by any means, but personally I'm big fan
of wrapping low-level code for use by scripting languages (like Scheme,
Perl or Python) for easier testing purposes (and doing lots of other
useful stuff), and on the other side I liked Autotest simplicity, so I
gave it a run.
Regards,
Alex