|
Boost : |
From: Edward Diener (eddielee_at_[hidden])
Date: 2002-10-30 19:08:43
"Terje Slettebø" <tslettebo_at_[hidden]> wrote in message
news:11d401c28067$abe6c650$60fb5dd5_at_pc...
> >From: "Edward Diener" <eddielee_at_[hidden]>
>
> > "David Abrahams" <dave_at_[hidden]> wrote in message
> > news:upttrai55.fsf_at_boost-consulting.com...
> > > "Edward Diener" <eddielee_at_[hidden]> writes:
> > >
> > > > I know that one can do a diff on each version of Boost to find out
> what
> > has
> > > > changed for a particular library, but I think that it would be very
> > helpful
> > > > for implementors using Boost to know what specifically has been
added
> or
> > > > changed for each library in explanatory form. Does this information
> > exist or
> > > > has such an idea ever been discussed before ?
> > >
> > > No, it hasn't AFAIK. However, I like it. It certainly sounds a lot
> > > more useful than per-header changelogs.
> >
> > Quite honestly I do not even see per-header changelogs in the headers at
> > which I am looking. Perhaps they can be generated when one pulls a file
> out
> > of CVS, but I don't see them appearing in the headers which are
> distributed.
>
> That's probably because it's adviced against that in the Boost
> recommendations. :) (http://www.boost.org/more/lib_guide.htm): "Including
> revision history in source files is no longer recommended; the publicly
> available CVS repository better serves that purpose."
>
> I think Dave referred to the CVS diffs.
I guess, therefore, that I will have to refer to the CVS diffs to determine
any changes made between revisions. I still feel that some documentation of
changes for each library would be valuable with each release.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk