|
From: | Riccardo Mottola |
Subject: | Re: Linux+GNUstep to Unit Test Objective-C Code instead of Mac+XCode? |
Date: | Tue, 07 May 2013 21:36:36 +0200 |
User-agent: | Mozilla/5.0 (X11; NetBSD i386; rv:17.0) Gecko/20130221 Thunderbird/17.0.2 |
Hi, On 05/07/13 21:23, Ibadinov Marat wrote:
That is a bit an extreme, isn't it? That would mean implementing and cloning all of cocoa and in all its versions.On May 3, 2013, at 3:11 AM, Ivan Vučica wrote:If your primary goal is testing Cocoa code, keep in mind that there may be differences between GNUstep and Cocoa. But, everyone should be writing code that runs on both GNUstep and Cocoa, anyway, so that's not a problem, right? :-)I wonder if this is the official policy of GNUstep project. Or maybe the following is more appropriate: GNUstep should be developed in such way that each and every piece of code that works on top of Cocoa should work correctly using GNUstep, requiring no single change at all?
Ivan's statement is more sensible. But also too extreme, it would mean that GNUstep can't have its own stuff, which, I think, it should.
I know others may disagree, but for me GNUstep should implement a certain subset, as large as possible, of useful Apple classes and do that in a portable and platform-agnostic way. GNUstep shall also implements its own classes, methods and extensions. What must be guaranteed is that the common (and documented) subset common to GNUstep and Cocoa behaves correctly as Apple's implementation, so that no code changes are needed. Ideally all this should be tested by a repeatable test suite.
Riccardo
[Prev in Thread] | Current Thread | [Next in Thread] |