On Mar 14, 2013, at 4:51 PM, Luther Baker wrote:
> but more
> recently, several seniors Obj-C devs have suggested that they prefer
> #import in the .h files.
Oh god, no. Who says that?! Importing a header just because it defines a class
you’re using is a major waste. The only times you should
On Mar 14, 2013, at 4:51 PM, Luther Baker wrote:
> Given today's computing power, is there a strong case that can be made for
> or against the general use of forward declarations?
>
> I grew up using them as a best practice in C++ projects ... but more
> recently, several seniors Obj-C devs have
On Thu, Mar 14, 2013, at 04:51 PM, Luther Baker wrote:
> Given today's computing power, is there a strong case that can be made
> for
> or against the general use of forward declarations?
>
> I grew up using them as a best practice in C++ projects ... but more
> recently, several seniors Obj-C dev
On Mar 14, 2013, at 18:52, "Luther Baker" wrote:
> Given today's computing power, is there a strong case that can be made for
> or against the general use of forward declarations?
It really depends on the size of your project. The projects I've worked on
throughout my career would be slow as mu
Given today's computing power, is there a strong case that can be made for
or against the general use of forward declarations?
I grew up using them as a best practice in C++ projects ... but more
recently, several seniors Obj-C devs have suggested that they prefer
#import in the .h files.
Initial
