I think the correct solution is to allow something like this:
@classNSObject GSStackTrace;
This would forward-declare the class, and also advertise that
it conforms to the NSObject protocol.
It's an interesting suggestion, and has good merit. :-)
I would personally not like it that much
On 10 Apr 2011, at 12:30, Nicola Pero wrote:
If you message an object of a class which is only declared using @class,
you should get a warning. Both GCC and clang don't warn about this.
I think clang does. The problem is that, in this case, it never sees that the
instances are of
If you message an object of a class which is only declared using @class,
you should get a warning. Both GCC and clang don't warn about this.
I think clang does.
On my machine, all compilers (both GCC and clang from trunk, as far as I can
see)
compile the following testcase with no
Hey Ivan,
Let me know if I can help you get Gorm building.
GC
P.S. My internet connection is down, my provider is coming tomorrow to
fix the issue so I should be able to help on Tuesday.
On Fri, Apr 8, 2011 at 4:42 PM, Ivan Vučica ivuc...@gmail.com wrote:
Hi,
In interests of sharing current
I'm writing this using m 3G/4G connection.. :)
On Sun, Apr 10, 2011 at 1:55 PM, Gregory Casamento
greg.casame...@gmail.com wrote:
Hey Ivan,
Let me know if I can help you get Gorm building.
GC
P.S. My internet connection is down, my provider is coming tomorrow to
fix the issue so I should
Hi Ivan,
Awesome you got this working! With your portfiles I was able to get everything
up to gnustep-gui installed on a fresh installation of macports on OS X 10.6.6.
I had to fix some problems with the gnustep-back port (add some X library
dependencies to the Portfile, and attach a patch for
