On Oct 4, 2008, at 12:43 PM, Andrew Merenbach wrote:
On Oct 4, 2008, at 10:32 AM, Bill Bumgarner wrote:
Class extensions are also the one place where you can redeclare
that a property is readwrite.
Hi! Â Bill makes a very well-written explanation, but I beg to
append (in a very nit-picky fa
On Oct 4, 2008, at 10:32 AM, Bill Bumgarner wrote:
Class extensions are also the one place where you can redeclare that
a property is readwrite.
Hi! Bill makes a very well-written explanation, but I beg to append
(in a very nit-picky fashion) to this point, if only for the sake of
the a
On Oct 4, 2008, at 7:49 AM, Jonathan del Strother wrote:
To avoid those warnings, the method declaration or definition needs to
appear before it's used. Â I usually add a private category at the top
of my .m files where you can declare private methods - something like
this :
@interface BigLetter
Ah! That's it! I forgot about this order of declaration in C source
files.
Thanks,
Andre Masse
On Oct 4, 2008, at 10:49, Jonathan del Strother wrote:
I'm guessing that the times where it doesn't warn occur after "-
(void)prepareAttributes" ?
To avoid those warnings, the method declaration
On Sat, Oct 4, 2008 at 3:43 PM, Andre Masse <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Can someone explain to me why I get this compiler warning (BigLetterView is
> a subclass of NSView):
>
> 'BigLetterView' may not respond to '-prepareAttributes'
>
>
>
> - (id)initWithFrame:(NSRect)rect {
>
>if(
Hi,
Can someone explain to me why I get this compiler warning
(BigLetterView is a subclass of NSView):
'BigLetterView' may not respond to '-prepareAttributes'
- (id)initWithFrame:(NSRect)rect {
if(![super initWithFrame:rect]) {
return nil;
}