Re: [boost] [modular boost] non-linked headers

Subject: Re: [boost] [modular boost] non-linked headers
From: Beman Dawes (bdawes_at_[hidden])
Date: 2013-12-02 21:02:38

On Mon, Dec 2, 2013 at 7:11 PM, Daniel James <daniel_at_[hidden]> wrote:

> On 3 December 2013 00:08, Bjørn Roald <bjorn_at_[hidden]> wrote:
> >
> > yes, but b2 headers create hard links
>
> It really should use soft links. Most programs don't change files in
> place, so as soon as such a change is made the two entries will be
> pointing to different inodes. Which defeats the purpose, since they
> should always be the same.
>

I'm missing something. Could you give an example of what you mean by "Most
programs don't change files in place"? Hard links ensure that a change is
always seen by both the entries because there is only one underlying file.
I ran into that with Visual Studio when I tried symlinks and found that as
a result Visual Studio failed to realize when a dependency had changed.

--Beman