• 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: Distributing vs. re-using source code?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Distributing vs. re-using source code?


  • Subject: Re: Distributing vs. re-using source code?
  • From: "M. Uli Kusterer" <email@hidden>
  • Date: Wed, 15 Sep 2004 04:43:19 +0200

At 3:26 Uhr +0200 15.09.2004, Allan Odgaard wrote:
You can do that if you use CVS or similar. So you'd do a CVS import of the component you want to use, this allows you to use different versions of the same component in different projects (which is an advantage if updating a component has the chance of breaking one or more projects).

Guess I have another opportunity to take advantage of that book on Subversion I have ...


Another approach is to use symbolic links,

Yeah, that occurred to me as I mentioned Aliases. I'd have to create a nice tool for making links, though. Finder doesn't let me create them, and I'd hate to have to drop down to the command line every time.


add the files to your Xcode project w/o asking it to do a copy,

That's what I'm doing right now, but I still have to track down all those files in my project that aren't in the project folder when I want to distribute a copy.


or put your various stuff in a framework which you link with.

Yes, though due to the diversity of all those classes, that wouldn't really be a good idea in my case. People would be annoyed at having to drag in an entire framework just for two or three classes...


I think this problems plagues us all...

Stop that. Sentences like these start me writing software... and I already have enough projects right now :-)


I find that the biggest barrier to reusability is how easy it is to reach from scratch projects, so I've set it up so that my stuff is in the default include path (much of my stuff is in the form of STL algorithms and containers, which are all in the header) and new projects already have my own frameworks added to the build process.

Not really my problem. At least not in Cocoa. Since I've been doing Cocoa, I've managed to write so many reusable classes that it's scary. I already started annoying a pal by making suggestions how he could make his code more self-contained. I don't know, but the design of the frameworks really starts to rub off on me in a nice way.


 But thanks for the input, I'll probably look into Symlinks some more.
--
Cheers,
M. Uli Kusterer
------------------------------------------------------------
       "The Witnesses of TeachText are everywhere..."
                   http://www.zathras.de
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Distributing vs. re-using source code?
      • From: Nick Zitzmann <email@hidden>
References: 
 >Distributing vs. re-using source code? (From: "M. Uli Kusterer" <email@hidden>)
 >Re: Distributing vs. re-using source code? (From: Allan Odgaard <email@hidden>)

  • Prev by Date: Re: Breaking source file into multiple files?
  • Next by Date: Re: Breaking source file into multiple files?
  • Previous by thread: Re: Distributing vs. re-using source code?
  • Next by thread: Re: Distributing vs. re-using source code?
  • Index(es):
    • Date
    • Thread