From: Jonathan Turkanis (technews_at_[hidden])
Date: 2004-08-21 15:41:00
"Carlo Wood" <carlo_at_[hidden]> wrote in message
> On Sat, Aug 21, 2004 at 07:39:43AM -0400, David Abrahams wrote:
> > When proposing design changes, first you have to describe the
> > problems your changes are designed to solve, or nobody will
> > understand the motivation.
> If you are not aware of the problems with boost::filesystem
> then I just give up immdeately, instead of wasting my time
> by trying to convince you about the need for a redesign.
> I've seen several people already agreeing that there is a design
> problem with the current boost::filesystem.
This is a good way to have your future suggestions ignored.
Since filesystem already has many users, you'll need to convince more
than 'several people' that there is a problem before your proposal is
accepted. Furthermore, how do you know that those people see the same
problems as you do, if you're not willing to spell out in detail
exactly what the problems are?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk