• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Refactoring a #define definition
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Refactoring a #define definition


  • Subject: Re: Refactoring a #define definition
  • From: Scott Ribe <email@hidden>
  • Date: Sat, 25 Jul 2015 19:35:19 -0600

On Jul 25, 2015, at 2:11 PM, Michael David Crawford <email@hidden> wrote:
>
> I find some benefit in refactoring the hard way, without the aid of automated tools.  This because having to think harder enables me to understand the code better, maybe find other opportunities for improving it.

I tend to take a middle road. Change that which I wish to refactor so that it produces compilation errors, check them out, then figure things out.

--
Scott Ribe
email@hidden
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice






 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >Re: Refactoring a #define definition (From: Carl Hoefs <email@hidden>)
 >Re: Refactoring a #define definition (From: Quincey Morris <email@hidden>)
 >Re: Refactoring a #define definition (From: Carl Hoefs <email@hidden>)
 >Re: Refactoring a #define definition (From: Michael David Crawford <email@hidden>)

  • Prev by Date: Re: Refactoring a #define definition
  • Next by Date: Re: Suggestion for XCode Groups
  • Previous by thread: Re: Refactoring a #define definition
  • Next by thread: Re: Refactoring a #define definition
  • Index(es):
    • Date
    • Thread