Fixed-sized array constructor can have unintended consequences

[boost@…]

As initially reported here: ​http://article.gmane.org/gmane.comp.lib.boost.devel/208444

The fixed-size array constructor takes the whole array, not accounting for possible null-terminators in the array.

Here is a more obvious test case that shows the problem:

void
array_ctor_test()
{
    char buf[256];
    strcpy(buf, "mydir/mysubdir");
 
    bfs::path p1(buf);
    bfs::path p2(&buf[0]);
    assert(p1 == p2); // Passes, because char-compares up to null
 
    p1 /= "extra";
    p2 /= "extra";
    assert(p1 == p2); // fail
}

[Beman Dawes]

This was fixed by changeset 64986, August 24, 2010.

Thanks,

--Beman