bug-libmatheval
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-libmatheval] tiny texinfo patch


From: Ed Hill
Subject: Re: [Bug-libmatheval] tiny texinfo patch
Date: Tue, 3 Oct 2006 13:30:32 -0400

On Tue, 3 Oct 2006 11:17:52 +0200 "Aleksandar B. Samardzic"
<address@hidden> 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:

Hi Alex,

Thanks!  I'll take a look later this week or this weekend.


> - Missing texinfo entries are added, but I used "GNU libraries" as
> value for "@dircategories" entry, because it seemed most appropriate
> to me (I checked on my Slackware installation and also on a Debian
>   installation and "Development" and "GNU libraries" categories seemed
>   only alternatives, so I decided for later, but certainly I'd like to
>   hear any other suggestion).

That's cool.  The heading I put was just a placeholder--something
thrown in that seemed vaguely plausible.  :-)


> - There was real problem with testing functions, unrelated to
>   deprecation messages printed to stderr (stderr output is set to be
>   ignored in test scripts anyway).  Namely, two tests were producing
>   infinity value and seems like Guile changed printing of this value
>   from "#.#" (that test script was expecting) to "inf.0" between 1.6.x
>   and 1.8.0 release...  Anyway, I've changed tests, so that "make
> check" should work now with both 1.6.x and 1.8.0 Guile releases.
> Issue with using of Guile deprecated features should be certainly
> fixed sometimes, but for now (since 1.8.x Guile branch doesn't yet
> seem particularly stable or widely used) I won't change anything in
> the libmatheval Guile wrappers regarding this.

Oh, OK, I didn't understand the actual failures.

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?

thanks again,
Ed

-- 
Edward H. Hill III, PhD  |  address@hidden  |  http://eh3.com/

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]