Re: Xcode-users Digest, Vol 5, Issue 396
Re: Xcode-users Digest, Vol 5, Issue 396
- Subject: Re: Xcode-users Digest, Vol 5, Issue 396
- From: Chris Espinosa <email@hidden>
- Date: Wed, 25 Jun 2008 13:44:28 -0700
On Jun 25, 2008, at 1:17 PM, Daniel Lord wrote: Pardon me in advance this seems cheeky, but why can't Apple just permanently define names for clearly permanent values like USERNAME, TARGETNAME, PROJECTNAME, ORGANIZATIONNAME, TIME, FILENAME, DATE, UUID, ? Why the heck does Apple need to reserve the right to change those names at whim to the detriment of people who want to take advantage of template customization? How about some stability? Apple going to drop project names for instance? I don't get it--can you help me understand the strategy here?
Because we recognize the many and inherent limitations of the current template-instantiation engine; we've had an idea on our drawing board for years to completely replace it with something newer, simpler, cleaner, and more useful; that our plans for that have been pushed out repeatedly by the requirements to support iPhone development, Leopard, Intel, Core Data, ad nauseum; and we'd rather dedicate our documentation resources to things that are more immediately useful and/or planned to be stable in the long run. There are many de facto extension points like this in Xcode, and the general rule is that if it isn't formally documented, then we expect that some future Xcode is going to break it. The only variable is the definition of "future."
Chris |
_______________________________________________
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