Re: Properties: A question of style

> 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) BOOLfoo; > > > Is there a

Re: Properties: A question of style

On Jun 14, 2016, at 18:55 , Steve Mills wrote: > > Why are you using a getter as a setter? I’m not. I’m saying, as far as I’m concerned, the property is “isAnimal”, not “animal”. (Obviously, in the case of an existing property for an existing class, I have to use whatever forms the class dec

Re: Properties: A question of style

> 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 concrete, say: > >self.enabled = YES; >

Re: Properties: A question of style

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; even when it’s something le

Re: Properties: A question of style

> 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) Please do not post admin req

Re: Properties: A question of style

> 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 foo; > > > Is th

Properties: A question of style

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 read/

Re: DNS resolution for apps vs Terminal?

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 wa

UINavigationController back gesture animation

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 th

Re: KERN_INVALID_ADDRESS

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 its state to see why it went wrong. > > > I would do tha

Re: DNS resolution for apps vs Terminal?

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 curl, both succeed. >> >> How are these two

Re: KERN_INVALID_ADDRESS

> 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 machine. It crashes on two cust

Re: DNS resolution for apps vs Terminal?

> 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 other apps are using the fr

Re: TableView crash with Delegate

> 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 - (__kindofNSView

Re: TableView crash with Delegate

> 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 problem: awakeFromNib gets called twice: once before

Re: DNS resolution for apps vs Terminal?

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 reported DNS failures. > > But

DNS resolution for apps vs Terminal?

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

Re: TableView crash with Delegate

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. > This obviously create

Re: KERN_INVALID_ADDRESS

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 wrong. Kind regards, Alastai