AlisdairM | 1 Jan 2007 01:35

Now config macro : BOOST_NO_TWO_PHASE_NAME_LOOKUP

I have just supplied John with a new defect macro and test case to
detect compilers that (do not) support 2-phase name lookup with
templates, but it would be really helpful if someone who is more
familiar with the problem (and access to conforming compilers!) can
verify the test for us!

The test case is in

boost/libs/config/boost_no_two_phase_name_lookup.ipp

and currently the code looks like:

template< class T >
struct base {
    int call() {
        return 1;
    }
};

int call() {
    return 0;
}

template< class T >
struct derived : base< T > {
    int call_test() {
        return call();
    }
};

(Continue reading)

Roland Schwarz | 1 Jan 2007 15:46
Picon

Re: [thread][string-algp][1.34] Doc build

John Maddock wrote:
> There are a couple of warnings from both the string-algo and thread lib doc 
> builds that look like they might be errors:
> 
> Citation to nonexistent publication abbrev:
> Citation to nonexistent publication abbrev:
> 
> Any ideas?  Presumably something common to both libs?

I am trying to look into this (for thread).

However the doc build process does look to me like black magic. Also I 
could not find anywhere the rationale why building the docs does 
overwrite files that are under source control.

I am trying to compile the doc from BOOST_ROOT/doc. Is this the wrong place?

Then the process generates files under bin.v2, which is what I expected.
But surprisingly also files under:

doc/xml
doc/html
and under libs/

are generated. Even uglier: some files which are under source control 
are overwritten!

Nevertheless the docs were built, and I logged everything. Nowhere I 
could find the "Citation to nonexistent publication abbrev:".

(Continue reading)

John Maddock | 1 Jan 2007 16:45
Picon

Re: [thread][string-algp][1.34] Doc build

> I am trying to look into this (for thread).
>
> However the doc build process does look to me like black magic. Also I
> could not find anywhere the rationale why building the docs does
> overwrite files that are under source control.
>
> I am trying to compile the doc from BOOST_ROOT/doc. Is this the wrong
> place?

Nope, that's where I built from.

> Then the process generates files under bin.v2, which is what I
> expected.
> But surprisingly also files under:
>
> doc/xml
> doc/html
> and under libs/
>
> are generated. Even uglier: some files which are under source control
> are overwritten!

Yep, we have "placeholders" that redirect to the nightly doc build, but when 
the release is put together these get overwritten with the "true" versions.

> Nevertheless the docs were built, and I logged everything. Nowhere I
> could find the "Citation to nonexistent publication abbrev:".
>
> How did you get this?

(Continue reading)

Roland Schwarz | 1 Jan 2007 17:05
Picon

Re: [thread][string-algp][1.34] Doc build

John Maddock wrote:
> Yep, we have "placeholders" that redirect to the nightly doc build, but when 
> the release is put together these get overwritten with the "true" versions.

This however makes the process somewhat obscure during authoring however...

> Just as you did: built from /doc under win32 on the release branch.  I've 
> just done another cvs update so I'll try again.

What I found so far:

For thread there is an entity.xml file which is beeing used for "short 
hand" citations too. I just tried to check by hand for missing ones. 
Nope :-(
Is it possible that I do not get the errors, since I am trying the build 
from linux? Perhaps the tools are different?

Btw.: There are so much errors or messages, looking like errors, that I 
simply wouldn't see the one you are pointing at when not trying to 
specifically filter for it.

To me the whole doc build process looks surprising anyway. The surprise 
is, that I end up having some readable docs despite the long warning and 
"error" listsings. But this might be specific to linux. If so, perhaps 
an indication, that the doc build process doesn't port easily?

Btw.: Did you ever try to build bjam pdf for the whole library?

Roland

(Continue reading)

John Maddock | 1 Jan 2007 17:21
Picon

Re: [thread][string-algp][1.34] Doc build

> Nevertheless the docs were built, and I logged everything. Nowhere I
> could find the "Citation to nonexistent publication abbrev:".
>
> How did you get this?

Looking into this some more, I think I only saw this because I'm using 
Bleeding-edge stylesheets, there is some discussion here 
http://www.oasis-open.org/archives/docbook-apps/200609/msg00021.html 
regarding whether the behaviour is correct or not.  The warning is issued if 
you have a citation to a non-existant entity, but unhelpfully doesn't tell 
you which one :-(  My gut feeling is that the warning might indicate a typo 
in the XML but I haven't tracked anything down yet... trying again with the 
very latest stylesheets.

John. 

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

John Maddock | 1 Jan 2007 17:23
Picon

Re: [thread][string-algp][1.34] Doc build

Roland Schwarz wrote:
> What I found so far:
>
> For thread there is an entity.xml file which is beeing used for "short
> hand" citations too. I just tried to check by hand for missing ones.
> Nope :-(
> Is it possible that I do not get the errors, since I am trying the
> build
> from linux? Perhaps the tools are different?
>
> Btw.: There are so much errors or messages, looking like errors, that
> I simply wouldn't see the one you are pointing at when not trying to
> specifically filter for it.

Tell me about it :-(

> To me the whole doc build process looks surprising anyway. The
> surprise
> is, that I end up having some readable docs despite the long warning
> and "error" listsings. But this might be specific to linux. If so,
> perhaps
> an indication, that the doc build process doesn't port easily?

The main problems are messages relating to missing linkends: those indicate 
broken links.

> Btw.: Did you ever try to build bjam pdf for the whole library?

No!  Runs screaming to the hills....

(Continue reading)

Douglas Gregor | 1 Jan 2007 18:00
Picon
Picon
Favicon

Boost regression notification (2007-01-01 [RC_1_34_0])

Boost Regression test failures
Report time: 2007-01-01T13:56:04Z

This report lists all regression test failures on release platforms.

Detailed report:
  http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/issues.html

11 failures in 5 libraries
  concept_check (6)
  date_time (1)
  regex (1)
  test (2)
  utility (1)

|concept_check|
  class_concept_fail_expected:  borland-5.6.4  borland-5.8.2  borland-5.8.2  msvc-6.5  msvc-6.5  msvc-7.0

|date_time|
  testgenerators:  qcc-3.3.5_gpp

|regex|
  regex_regress_threaded:  msvc-6.5

|test|
  prg_exec_fail2:  darwin-4.0.1
  prg_exec_fail3:  cw-9.4

|utility|
  operators_test:  gcc-3.4.5_linux_x86_64
(Continue reading)

Rene Rivera | 1 Jan 2007 18:03
Picon
Gravatar

Boost inspection notification (2007-01-01/RC_1_34_0) *X*

Boost Inspection Report
Run Date: 17:02:49 UTC, Monday 01 January 2007

An inspection program <http://www.boost.org/tools/inspect/index.html>
checks each file in the current Boost CVS for various problems,
generating this as output. Problems detected include tabs in files,
missing copyrights, broken URL's, and similar misdemeanors.

Totals:
  11376 files scanned
  888 directories scanned (including root)
  187 problems reported

Problem counts:
  0 files with invalid line endings
  0 bookmarks with invalid characters
  4 invalid urls
  116 broken links
  26 unlinked files
  4 file/directory names issues
  2 files with tabs
  0 violations of the Boost min/max guidelines
  35 usages of unnamed namespaces in headers (including .ipp files)

Summary:
  archive (3)
  bind (1)
  boost-root (1)
  build (2)
  date_time (1)
(Continue reading)

Rene Rivera | 1 Jan 2007 18:03
Picon
Gravatar

Boost inspection notification (2007-01-01/RC_1_34_0) *LC*

Boost Inspection Report
Run Date: 17:03:00 UTC, Monday 01 January 2007

An inspection program <http://www.boost.org/tools/inspect/index.html>
checks each file in the current Boost CVS for various problems,
generating this as output. Problems detected include tabs in files,
missing copyrights, broken URL's, and similar misdemeanors.

Totals:
  11376 files scanned
  888 directories scanned (including root)
  993 problems reported

Problem counts:
  623 files missing Boost license info or having wrong reference text
  370 files missing copyright notice

Summary:
  any (1)
  archive (1)
  boost-root (1)
  build (60)
  concept_check (22)
  conversion (5)
  filesystem (2)
  function (1)
  graph (1)
  inspect (1)
  integer (9)
  lambda (10)
(Continue reading)

John Maddock | 1 Jan 2007 18:08
Picon

Re: [thread][string-algp][1.34] Doc build

Roland:  I've decided this must be a red-herring, I've tracked down the 
<citation> entries in the docbook XML that generate the warning, and they 
*do* lead to valid links in the html, so I think we can ignore this one, 
although I admit I don't really know what does and does not cause the 
warning.

Apologies for the noise!

John. 

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost


Gmane