On 06/04/10 07:58, strk wrote:
> Could you please say more about what you don't like about
> the check API ? I said what I like about it. Will repeat it:
> the 'check' API reports both success/failure both
> expected/obtained results in case of failure.
I dislike the check API for being overly terse. Being the author of
DejaGnu (and the GCC, GDB, Binutils testsuites), I prefer that API of
course. :-) We're not going to depreciate the DejaGnu testing API, so
just get used to it. You don't have to use it, and both APIs co-exist
just fine. The other big point about using the DejaGnu API is that then
our testsuites automatically support cross testing on embedded
platforms. Although we currently don't use this feature, we could, and
in the future we might.
> In the specific case detected by Ben, if we were using check_equals
> we would see as part of the failure message the results obtained with
> the proprietary player, which should become what we expect.
Which can be done with the DejaGnu API as well. I'm really into not
arguing about this... Just please accept that we use both APIs, and will
continue to do so.
- rob -
_______________________________________________
Gnash-dev mailing list
Gnash-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnash-dev
