[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: Stephen Davis <stephendavis_at_mac.com>
Date: 2005-08-06 02:50:10 CEST

On Aug 1, 2005, at 2:59 PM, Rick Mann wrote:

> 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).

As noted in another email, a long-time Mac user would expect his open
file to follow the rename. It's a feature, one that I personally
like a lot. YMMV.

>> 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.

Rick, not that this will solve your problem directly but you might
want to check out my Subversion plugin for CodeWarrior. Since it
notifies the IDE before running a subversion operation, the IDE will
close any open files and re-open them which should solve your problem.


I have not yet updated it for Subversion 1.2.1 (I've been swamped at
work) but that release was mostly locking fixes from the client's
perspective so it may not be relevant to you. Lemme know if you
desperately need the fixes in 1.2.1 and I'll see about getting a new
version out.


P.S. Ignore the part of the release notes that say it might not work
on Panther, it does.
Received on Sat Aug 6 08:13:27 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.