Search Results

In Objective-C, all object references are optional. Because of this, code like you posted is silly. if (variable != nil) { [variable doThing]; } Code like the above is unheard of in Objective-C …

The Uniform Access Principle tells us that: All services offered by a module should be available through a uniform notation, which does not betray whether they are implemented through storage …

The basic class in such an app will be an "Appointment" or "Event" class. It will contain the date/time and place of the meeting, who will be there, whether a reminder alarm should sound, whether the …

You don't need an interface for User to derive from. User is effectively plain old data. However, you should have an interface for your ShowUserInfo class because it provides a side effect that you wi …

I'm currently dealing with a SOAP API and it's corresponding WSDL. After looking over the JSON API specs. I get the impression that they are trying to be a WSDL equivalent for REST JSON servers. Like …

You say that you don't want to move the projectsDAO.fetchProjects out of this constructor because then "... almost all of the logic would have to be done before the constructor is called..." but it se …

You say, "... this implementation only moves the if-else from inside to outside" as if that's no big deal but in fact the second example moves the if check closer to the code that knows what the boole …