This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: More Objective C @"string" bugs...


Nicola,

I think this is a great idea! Can you try implement these tests? I'd
be more than willing to incorporate them in the Objective-C testsuite.

Thanks,
Ovidiu

On Tue, 6 Mar 2001 15:52:42 +0100 (CET), Nicola Pero <n.pero@mi.flashnet.it> wrote:

> > > As a newcomer to gcc development, the fact that an existing working
> > > frontend (correct code!) is broken silently and randomly by gcc core
> > > development commits seems to me a wicked combination of ugly program
> > > design and - particularly in the case of frontends which are kept in the
> > > gcc repository - very bad habits of some gcc hackers who don't take into
> > > account the existence and importance of front ends different from C/C++.
> > 
> > GCC developers follow the standard procedure of running the testsuite and
> > avoiding regressions - it's simply that the ObjC testsuite is very small
> > so problems are likely not to be shown up.  
> 
> If that would help, I can write a couple of tests for each of the
> objc-specific constructs (probably using the list given in the specs).
> That would take me approximately half a day and give a round coverage of
> fairly most of Objective-C.  I already know we won't (shouldn't) get any
> new failures - but if having a comprehensive testsuite helps developers to
> check that they don't break objective-c when they make changes - I would
> be more than happy to produce such a set of tests. 
> 
> Can you confirm that you are interested in such a work - as I will not
> start writing a full set of tests if I am not sure they will be used.
> 
> 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]