Re: Xcode dependency handling
Re: Xcode dependency handling
- Subject: Re: Xcode dependency handling
- From: Chris Page <email@hidden>
- Date: Mon, 5 Feb 2007 17:43:42 -0800
On Feb 5, 2007, at 16:41 PM, Marshall Clow wrote:
Here's an example of how it could work w/o doing that:
1) You hit build.
2) Xcode writes all changed files out to /tmp/501/<ProjectName>/ -
but doesn't mark them as "saved".
3) Xcode builds your project; preferentially using files in that /
tmp directory instead of the ones that are in your local directory.
4) <Some other stuff needs to be remembered so that _the next
build_ works>
Yes, please. Coincidentally, I was thinking about this recently.
Another possibility is to memory map the files. While editing, the
currently visible contents would also be visible to any process
reading the files†. When you save a modified file, it doesn't
actually have to do anything. Closing a file without saving it would
involve restoring the original contents, possibly by applying all the
Undos since the file was last saved, or perhaps by mapping the file
using copy-on-write so the original pages are retained somewhere
until the file is closed (not sure whether that's possible).
† Memory-mapped files participate in the unified VM and file caching
systems. If you mmap a file and modify it, then open the file and
read it, you'll see the modified data even if it hasn't yet been
committed to storage.
--
Chris Page - Dylan Programmer
Open Source Dylan Compilers: <http://www.opendylan.org/>
_______________________________________________
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