Tag Info

New answers tagged

0

There's one special architecture they call VIPER (View, Interactor, Presenter, Entity and Routing). I'll try resume here what you need know: View they are dummy views; contain objects like UIView, UIViewController, UILabel, etc; waits the content from the Presenter; handle user interaction and pass it to Presenter layer. Presenter doesn't know UI ...


3

The main reason is that just because you're done with a local reference to an object doesn't mean you're finished with the object itself. For example, if your function creates an object and adds it to a pre-existing collection that belongs to a broader scope, then the object has to be on the heap; anything on the stack gets trashed after the function ...


0

It's an implementation detail of the Apple/GNUstep/OpenStep Objective-C runtime. libobjc is the Apple Objective-C runtime, and Cocoa/GNUstep classes like NSObject are tied to that Objective-C runtime. Objective-C (originally) just adds a minimal layer of syntax on top of C, and there's no reason, from a pure Objective-C language point of view, that objects ...



Top 50 recent answers are included