[gccsdk] Symlinking instead of copying?

Sebastian Maus maus at acorn.de
Mon Feb 4 00:54:51 PST 2008


--On February 3, 2008 14:24:12 -0800 Peter Naulls <peter at chocky.org> wrote:
> John Tytgat wrote:
[using hardlinks]
>> I just happen to have reverted that local change after dismissing this
>> as a possible improvement.  Or do you know a way to overcome that
>> problem ?
> Yes, use symlinks ;-)   This will do the right thing in almost all 
> cases.  Certainly I've edited symlinked files under a wide variety of
> Unix editors, and also via SunFish, with no obvious detriment.

I think the effects would be the same, as I suspect there's an unlink()
being called before the "new" file is opened. In this case, a hardlink will
have the same effect as a symlink.
This essentially depends on the behaviour of the editor involved, of course.


More information about the gcc mailing list