> On 15.06.2016, at 01:48, Graham Cox wrote:
>
> Hi all,
>
> Just a quick point for discussion.
>
> Suppose I have a read-only BOOL property. What’s better, to declare it as:
>
> @property (readonly) BOOL isFoo;
>
> or:
>
> @property (readonly, getter=isFoo) BOOL
> On Jun 14, 2016, at 20:51, Quincey Morris
> wrote:
>
> FWIW, I prefer to use the other form for setters, too. I don’t see why:
>
>self.animal = YES;
>
> is any improvement over:
>
>self.isAnimal = YES;
>
> even when it’s something less
On Jun 14, 2016, at 16:48 , Graham Cox wrote:
>
> n.b. I’d always use the latter form for read/write properties
FWIW, I prefer to use the other form for setters, too. I don’t see why:
self.animal = YES;
is any improvement over:
self.isAnimal = YES;
> On Jun 14, 2016, at 19:45, Charles Srstka wrote:
>
> if thisArray.empty { doSomething() }
That's not what he suggested as the 2nd form. Look again.
Steve via iPad
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> On Jun 14, 2016, at 6:48 PM, Graham Cox wrote:
>
> Hi all,
>
> Just a quick point for discussion.
>
> Suppose I have a read-only BOOL property. What’s better, to declare it as:
>
> @property (readonly) BOOL isFoo;
>
> or:
>
> @property (readonly, getter=isFoo) BOOL
Hi all,
Just a quick point for discussion.
Suppose I have a read-only BOOL property. What’s better, to declare it as:
@property (readonly) BOOL isFoo;
or:
@property (readonly, getter=isFoo) BOOL foo;
Is there any advantage to one over the other? n.b. I’d always use the latter
form for
Thanks for the answers. Sigh.
A little more investigation showed that it had something to do with my router's
DNS cache. Normally, it serves up itself as the DNS server for DHCP clients.
When I reconfigured it to serve up Google's DNS servers instead, all apps
started working normally.
This
Since iOS7 we have the back gesture to go up the navigation stack. The
gesture basically controls the push/pop animation. We can basically pick
the controller and go back and forth in the animation phases.
Does anyone see a good way to piggyback onto that?
I would like to have another animation
On 14 Jun 2016, at 16:36, Raglan T. Tiger wrote:
>
>> On Jun 14, 2016, at 2:51 AM, Alastair Houghton
>> wrote:
>>
>> Run your program in the debugger; it will stop when it tries to access the
>> invalid address and you can investigate
On 14 Jun 2016, at 15:13, Michael Nickerson wrote:
>
>> On Jun 14, 2016, at 5:11 AM, Rick Mann wrote:
>>
>> Just now Safari stopped being able to load facbook.com. So did Chrome. Both
>> reported DNS failures.
>>
>> But dig on the command line, and
> On Jun 14, 2016, at 2:51 AM, Alastair Houghton
> wrote:
>
> Run your program in the debugger; it will stop when it tries to access the
> invalid address and you can investigate its state to see why it went wrong.
I would do that but it does not crash on my
> On Jun 14, 2016, at 5:11 AM, Rick Mann wrote:
>
> Just now Safari stopped being able to load facbook.com. So did Chrome. Both
> reported DNS failures.
>
> But dig on the command line, and curl, both succeed.
>
> How are these two domains different?
>
Safari and
> On 14 Jun 2016, at 12:26, Gerriet M. Denkmann wrote:
>
>
> But no problem, as long one keeps in mind (as you recommended) that
> awakeFromNib “can get called many times”.
>
You may be experiencing this, as described in docs for view based table views:
NSTableView -
> On 14 Jun 2016, at 16:03, Alastair Houghton
> wrote:
>
> On 14 Jun 2016, at 05:33, Gerriet M. Denkmann wrote:
>>
>> But I had:
>> - (void)awakeFromNib
>> {
>> self.someUniqueObject = [ [ UniqueObject alloc ] init ];
>> }
>>
>> The
Really facbook.com ? If so, maybe it's some kind of protection, the site is
owned by MarkMonitor; perhaps there is a blocker on these things.
On 14 June 2016 at 10:11, Rick Mann wrote:
> Just now Safari stopped being able to load facbook.com. So did Chrome.
> Both
Just now Safari stopped being able to load facbook.com. So did Chrome. Both
reported DNS failures.
But dig on the command line, and curl, both succeed.
How are these two domains different?
--
Rick Mann
rm...@latencyzero.com
___
Cocoa-dev mailing
On 14 Jun 2016, at 05:33, Gerriet M. Denkmann wrote:
>
> But I had:
> - (void)awakeFromNib
> {
> self.someUniqueObject = [ [ UniqueObject alloc ] init ];
> }
>
> The problem: awakeFromNib gets called twice: once before
> applicationDidFinishLaunching:, once after.
On 13 Jun 2016, at 20:14, Raglan T. Tiger wrote:
>
> Or , how can an address held in a variable be checked for validity?
Run your program in the debugger; it will stop when it tries to access the
invalid address and you can investigate its state to see why it went
18 matches
Mail list logo