RE: Xcode dependency handling
RE: Xcode dependency handling
- Subject: RE: Xcode dependency handling
- From: "Syd Polk" <email@hidden>
- Date: Tue, 6 Feb 2007 09:40:05 -0600
> -----Original Message-----
> 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.
Memory-mapped files are not supported on all drives, particularly network
drives. Xcode has to support compiling files from any arbitrary file system.
_______________________________________________
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