[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Serious incompatibility between Subversion and Metrowerks CodeWarrior

From: Rick Mann <rmann_at_latencyzero.com>
Date: 2005-08-01 23:59:44 CEST

On Aug 1, 2005, at 2:37 PM, Dale Worley wrote:

> It's really an oddity for an editor to keep an open handle on a
> file. All
> (other) editors that I know of do open-read-close or open-write-
> close. In
> particular, this allows you to "rename away" the file while it is
> being
> edited, and the editor's save will create a new file (with the
> right name).
> Under the assumption that other processes might be mucking with the
> filesystem at the same time, it's inherently erroneous to keep an open
> handle and assume that it will continue to refer to the same file
> name.

I may be wrong when I claim CW keeps the file open. It may, instead,
keep a Mac OS Alias to the file, which is The Right Thing to Do on
the Mac. The Alias maintains a link to the file based on it's file ID
(inode #) and Volume Ref, and allows the file to be tracked no matter
what happens to its meta data (name, location, etc).

Note that this works in conjunction with the Mac OS practice of
conducting "safe saves" by atomically swapping the contents of a new
file with the old file, thereby preserving the Aliases that pointed
to the file.

Part of the problem in all this is that I still need to use
CodeWarrior 8.3, and it's becoming evident that there's no way in
hell I'll get a fix to "such an old" version.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 2 00:01:46 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.