[Top][All Lists]

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

Re: [Suggestion] GNUstep-test for quality control (WAS: Re: deferred dea

From: Chris B. Vetter
Subject: Re: [Suggestion] GNUstep-test for quality control (WAS: Re: deferred deallocation)
Date: Tue, 14 Oct 2003 20:20:55 -0700

On Tue, 14 Oct 2003 21:59:31 -0400
"Yen-Ju Chen" <address@hidden> wrote:
>   How well the gnustep-test can detect the bugs depends on how well it
>   is written.
>   We can just start some and add more when new bug is discovered.
>   Over the time, it will cover over every details.

Yes, but even a very well written test-suite will not be able to find
bugs, as in "the current implementation is broken by design because the
implementor has no f*cking idea how to implement it correctly in the
first place" bugs.

As a simple example (without pointing any fingers):
There is a method that Apple's documentation states as returning an
NSData, while GNUstep's implementation returns an NSString.

No big deal, mind you, but in the end it's a bug.

>   Typo is another issue and I prefer not to touch this one. :)

Sissy ;-)


reply via email to

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