headers
Daniel James | 10 Oct 00:30
Favicon

[1.37] Release Notes

Hello everyone,

The template for the 1.37.0 release notes are at:

http://svn.boost.org/svn/boost/website/public_html/beta/feed/history/boost_1_37_0.qbk

Please can you add the relevant details for your libraries. Or if you
prefer, just reply with the details and I'll add them for you. If you
wish to bring up anything else, please do it in a new thread because
it'll make life easier.

thanks for your help,

Daniel
Permalink | Reply |
headers
Gennaro Prota | 11 Oct 15:40
Favicon

Re: [1.37] Release Notes

Daniel James wrote:
> Hello everyone,
> 
> The template for the 1.37.0 release notes are at:
> 
> http://svn.boost.org/svn/boost/website/public_html/beta/feed/history/boost_1_37_0.qbk
> 
> Please can you add the relevant details for your libraries. Or if you
> prefer, just reply with the details and I'll add them for you. If you
> wish to bring up anything else, please do it in a new thread because
> it'll make life easier.

It would be great if you could add a few lines for dynamic_bitset:

   * Implemented constructor ['do-the-right-thing] dispatch, a la
     standard sequences (mimics resolution of library issue 438,
     currently in the [^C++0x] working paper)

   * Miscellaneous improvements to documentation, code examples and
     implementation details.

PS: I hope I understood correctly: I hadn't to start a new thread for
this, had I? :-)

--

-- 
Genny
Permalink | Reply |
headers
Daniel James | 12 Oct 19:32
Favicon

Re: [1.37] Release Notes

2008/10/11 Gennaro Prota <gennaro.prota <at> yahoo.com>:
>
> It would be great if you could add a few lines for dynamic_bitset:
>
>  * Implemented constructor ['do-the-right-thing] dispatch, a la
>    standard sequences (mimics resolution of library issue 438,
>    currently in the [^C++0x] working paper)
>
>  * Miscellaneous improvements to documentation, code examples and
>    implementation details.
>
> PS: I hope I understood correctly: I hadn't to start a new thread for
> this, had I? :-)

You understood perfectly, you can see the changes here:

http://beta.boost.org/users/news/version_1_37_0

thanks,

Daniel
Permalink | Reply |
headers
Gennaro Prota | 18 Oct 13:27
Favicon

Re: [1.37] Release Notes

Daniel James wrote:
> 2008/10/11 Gennaro Prota <gennaro.prota <at> yahoo.com>:
>> It would be great if you could add a few lines for dynamic_bitset:
>>
>>  * Implemented constructor ['do-the-right-thing] dispatch, a la
>>    standard sequences (mimics resolution of library issue 438,
>>    currently in the [^C++0x] working paper)
>>
>>  * Miscellaneous improvements to documentation, code examples and
>>    implementation details.
>>
>> PS: I hope I understood correctly: I hadn't to start a new thread for
>> this, had I? :-)
> 
> You understood perfectly, you can see the changes here:
> 
> http://beta.boost.org/users/news/version_1_37_0

Daniel, before sending you a little fix...: the "Dynamic Bitset"
link leads to

<http://beta.boost.org/doc/libs/1_36_0/libs/dynamic_bitset/dynamic_bitset.html>

(with "1_36_0"). Is that normal?

--

-- 
Genny
Permalink | Reply |
headers
Daniel James | 18 Oct 15:40
Favicon

Re: [1.37] Release Notes

2008/10/18 Gennaro Prota <gennaro.prota <at> yahoo.com>:
>
> Daniel, before sending you a little fix...: the "Dynamic Bitset"
> link leads to
>
> <http://beta.boost.org/doc/libs/1_36_0/libs/dynamic_bitset/dynamic_bitset.html>
>
> (with "1_36_0"). Is that normal?

Yes, the 1.37 documentation hasn't been uploaded yet.
Permalink | Reply |
headers
Gennaro Prota | 18 Oct 17:11
Favicon

Re: [1.37] Release Notes

Daniel James wrote:
> 2008/10/18 Gennaro Prota <gennaro.prota <at> yahoo.com>:
>> Daniel, before sending you a little fix...: the "Dynamic Bitset"
>> link leads to
>>
>> <http://beta.boost.org/doc/libs/1_36_0/libs/dynamic_bitset/dynamic_bitset.html>
>>
>> (with "1_36_0"). Is that normal?
> 
> Yes, the 1.37 documentation hasn't been uploaded yet.

OK (almost --I'm lost in all these dances :-)

Please, can you replace the existing notes with the following?

* [phrase library..[@/libs/dynamic_bitset/ Dynamic Bitset]:]
   * Constructor "do the right thing" dispatch, a la standard sequence 
containers
     (mimics the proposed resolution of
     [@http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#438 
library
     issue 438], currently in the [^C++0x] working paper)
   * Improvements to documentation, code examples and implementation.

If you are wondering what has changed, here we go:

   - the first link uses the "canonical" form libs/library_name/,
     without naming either index.htm[l] or dynamic_bitset.html;
     this is what I've been taught in the early days of Boost :-)
     If it doesn't work with the current website
(Continue reading)

Permalink | Reply |
headers
Gennaro Prota | 18 Oct 17:15
Favicon

Re: [1.37] Release Notes

Gennaro Prota wrote:
> Daniel James wrote:
>> 2008/10/18 Gennaro Prota <gennaro.prota <at> yahoo.com>:
>>> Daniel, before sending you a little fix...: the "Dynamic Bitset"
>>> link leads to
>>>
>>> <http://beta.boost.org/doc/libs/1_36_0/libs/dynamic_bitset/dynamic_bitset.html> 
>>>
>>>
>>> (with "1_36_0"). Is that normal?
>>
>> Yes, the 1.37 documentation hasn't been uploaded yet.
> 
> OK (almost --I'm lost in all these dances :-)
> 
> Please, can you replace the existing notes with the following?

Please, add a period at the end of the first sub-bullet, too
(all entries have one in the qbk file).

Pedantic-ly yours,
--

-- 
Genny
Permalink | Reply |
headers
John Maddock | 23 Oct 17:29

[1.37] Showstopper? Documentation pdf build broken.

Generation of pdf's from the docbook source appears to be terminally broken 
at present, for example:

fop.render.pdf 
..\..\..\bin.v2\libs\config\doc\msvc-8.0\debug\threading-multi\config.pdf
(document [system-id 
file:/c:/data/boost/boost/trunk/libs/config/doc/../../../bin.v2/libs/config/doc/msvc-8.0/debug/threading-multi/config.fo]
  (validate
    [error] Element 'fo:inline' cannot be a child of 'fo:flow'. Only 
block-level elements are permitted in this context.
    [validation total: 1 error]
Parse error: Invalid XSL FO source

'file:/c:/data/boost/boost/trunk/libs/config/doc/../../../bin.v2/libs/config/doc/msvc-8.0/debug/threading-multi/config.fo': 
1 error found during validation

The problem occurs with both FOP and XEP as the FO translator BTW.

Anyone know where to look for the problem?

John. 

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Permalink | Reply |
headers
Daniel James | 24 Oct 15:54
Favicon

Re: [1.37] Showstopper? Documentation pdf build broken.

2008/10/23 John Maddock <john <at> johnmaddock.co.uk>:
> Generation of pdf's from the docbook source appears to be terminally broken
> at present, for example:
>
> fop.render.pdf
> ..\..\..\bin.v2\libs\config\doc\msvc-8.0\debug\threading-multi\config.pdf
> (document [system-id
> file:/c:/data/boost/boost/trunk/libs/config/doc/../../../bin.v2/libs/config/doc/msvc-8.0/debug/threading-multi/config.fo]
>  (validate
>   [error] Element 'fo:inline' cannot be a child of 'fo:flow'. Only
> block-level elements are permitted in this context.
>   [validation total: 1 error]
> Parse error: Invalid XSL FO source
> 'file:/c:/data/boost/boost/trunk/libs/config/doc/../../../bin.v2/libs/config/doc/msvc-8.0/debug/threading-multi/config.fo':
> 1 error found during validation
>
> The problem occurs with both FOP and XEP as the FO translator BTW.
>
> Anyone know where to look for the problem?

I'm getting a similar error when I try building pdfs, but I'm also
getting it when using boost 1.35 and 1.36. Which could be a problem
with my setup (if the old versions still build for you, then it must
be), or it might be that something has changed in the docbook xsl (not
necessarily a bug, it could be an incorrect assumption in our
stylesheets). Are you using a recent version?

I'll experiment some more later on. I don't think any of the recent
changes to boostbook would be likely to cause this, although I could
have easily overlooked something.
(Continue reading)

Permalink | Reply |
headers
John Maddock | 24 Oct 17:06

Re: [1.37] Showstopper? Documentation pdf build broken.

Daniel James wrote:
>>> Anyone know where to look for the problem?
>>
>> I'm getting a similar error when I try building pdfs, but I'm also
>> getting it when using boost 1.35 and 1.36. Which could be a problem
>> with my setup (if the old versions still build for you, then it must
>> be), or it might be that something has changed in the docbook xsl
>> (not necessarily a bug, it could be an incorrect assumption in our
>> stylesheets). Are you using a recent version?
>>
>> I'll experiment some more later on. I don't think any of the recent
>> changes to boostbook would be likely to cause this, although I could
>> have easily overlooked something.

Hmmm, it's a weird one this: I had problems building on trunk, but not on 
the release branch about a month back, now I see the same results on both I 
*think*, but the problem is really capricious, sometimes it's there, 
sometimes it's not :-(

I'm using release 6370 of the docbook xsl stylesheets *I think*.  Probably I 
should update and try again, but I'm fairly sure it used to work...

John.
Permalink | Reply |
headers
John Maddock | 24 Oct 17:10

Re: [1.37] Showstopper? Documentation pdf build broken.

Daniel James wrote:
>> I'm getting a similar error when I try building pdfs, but I'm also
>> getting it when using boost 1.35 and 1.36. Which could be a problem
>> with my setup (if the old versions still build for you, then it must
>> be), or it might be that something has changed in the docbook xsl
>> (not necessarily a bug, it could be an incorrect assumption in our
>> stylesheets). Are you using a recent version?

Experimenting some more: I see the problem on Boost-1.35 as well.  I also 
note that I don't seem to have generated PDF's for Boost.Config previously, 
so I guess this may be an old issue after all....

John.
Permalink | Reply |
headers
Beman Dawes | 27 Oct 11:58
Favicon

Re: [1.37] Showstopper? Documentation pdf build broken.

John Maddock wrote:
> Daniel James wrote:
>>> I'm getting a similar error when I try building pdfs, but I'm also
>>> getting it when using boost 1.35 and 1.36. Which could be a problem
>>> with my setup (if the old versions still build for you, then it must
>>> be), or it might be that something has changed in the docbook xsl
>>> (not necessarily a bug, it could be an incorrect assumption in our
>>> stylesheets). Are you using a recent version?
> 
> Experimenting some more: I see the problem on Boost-1.35 as well.  I 
> also note that I don't seem to have generated PDF's for Boost.Config 
> previously, so I guess this may be an old issue after all....

So what do we do? Work on trying to resolve the problem, but go ahead 
with 1.37.0 more or less on schedule even if it isn't resolved?

1.37.0 is scheduled for Friday. I don't currently know of any reason to 
delay, although I've still got a lot of unread email from the past weekend.

--Beman
Permalink | Reply |
headers
John Maddock | 27 Oct 11:59

Re: [1.37] Showstopper? Documentation pdf build broken.

Beman Dawes wrote:
>> So what do we do? Work on trying to resolve the problem, but go ahead
>> with 1.37.0 more or less on schedule even if it isn't resolved?

I believe so yes: it appears to be an old issue not a new one as I first 
thought,

John.
Permalink | Reply |
headers
John Maddock | 27 Oct 17:24

Re: [1.37] Showstopper? Documentation pdf build broken.

John Maddock wrote:
>> Beman Dawes wrote:
>>>> So what do we do? Work on trying to resolve the problem, but go
>>>> ahead with 1.37.0 more or less on schedule even if it isn't
>>>> resolved?

OK, I've got to the bottom of this, if you have a link target, say:

[#my_target]

in quickbook at top level scope (ie not inside a section) then you end up 
with an <fo:inline> tag generated for the target that is outside of any 
<fo:block>, and hense the invalid XML FO.  I'm not sure if this is my bug, a 
quickbook issue, a docbook one, or an XSL one! :-(

Whatever, for now it was easier to just change the quickbook markup so it 
generated valid XML.

HTH, John.
Permalink | Reply |
headers
Daniel James | 27 Oct 20:17
Favicon

Re: [1.37] Showstopper? Documentation pdf build broken.

2008/10/27 John Maddock <john <at> johnmaddock.co.uk>:
>
> OK, I've got to the bottom of this, if you have a link target, say:
>
> [#my_target]
>
> in quickbook at top level scope (ie not inside a section) then you end up
> with an <fo:inline> tag generated for the target that is outside of any
> <fo:block>, and hense the invalid XML FO.  I'm not sure if this is my bug, a
> quickbook issue, a docbook one, or an XSL one! :-(
>
> Whatever, for now it was easier to just change the quickbook markup so it
> generated valid XML.

Sorry, I never got round to looking at this. I'm not sure but it's
probably a quickbook bug. Quickbook has always generated invalid
boostbook/docbook, but it's never been a problem before.

I think the problem is that quickbook is generating boostbook along
the lines of:

    <section>...
        <section>...</section>
        <anchor id="..." />
        <para>
        </para>
        <section>...</section>
    </section>

But anchors and paragraphs have to come before the sub-sections -
(Continue reading)

Permalink | Reply |
headers
Eric Niebler | 29 Oct 16:39

Re: [1.37] Showstopper? Documentation pdf build broken.

Daniel James wrote:
> 2008/10/27 John Maddock <john <at> johnmaddock.co.uk>:
>> OK, I've got to the bottom of this, if you have a link target, say:
>>
>> [#my_target]
>>
>> in quickbook at top level scope (ie not inside a section) then you end up
>> with an <fo:inline> tag generated for the target that is outside of any
>> <fo:block>, and hense the invalid XML FO.  I'm not sure if this is my bug, a
>> quickbook issue, a docbook one, or an XSL one! :-(

Quickbook is really just a simple text substitution engine. It does very 
little validation. But it's written with Spirit so it has a grammar. We 
could use the grammar to enforce *some* of the boostbook schema. For 
instance, we could change the grammar to enforce that anchors do not 
appear out of sections.

--

-- 
Eric Niebler
BoostPro Computing
http://www.boostpro.com
Permalink | Reply |
headers
Gennaro Prota | 12 Oct 12:27
Favicon

Re: [1.37] Release Notes

Daniel James wrote:
> Hello everyone,
> 
> The template for the 1.37.0 release notes are at:
> 
> http://svn.boost.org/svn/boost/website/public_html/beta/feed/history/boost_1_37_0.qbk
> 
> Please can you add the relevant details for your libraries. Or if you
> prefer, just reply with the details and I'll add them for you. If you
> wish to bring up anything else, please do it in a new thread because
> it'll make life easier.

Hi,

I'd have a couple of notes for dynamic_bitset. Would next week be too
late to post them here? That's, likely, no sooner than Wednesday.

Thanks.

--

-- 
Genny
Permalink | Reply |
headers
Daniel James | 12 Oct 19:34
Favicon

Re: [1.37] Release Notes

2008/10/12 Gennaro Prota <gennaro.prota <at> yahoo.com>:
>
> I'd have a couple of notes for dynamic_bitset. Would next week be too
> late to post them here? That's, likely, no sooner than Wednesday.

In addition to the other email? Anyway, next week's fine. The deadline
is the release. Although it can still be changed afterwards, it's just
a bit annoying for anyone who's subscribed to the RSS feed.

Daniel
Permalink | Reply |
headers
Gennaro Prota | 12 Oct 23:19
Favicon

Re: [1.37] Release Notes

Daniel James wrote:
> 2008/10/12 Gennaro Prota <gennaro.prota <at> yahoo.com>:
>> I'd have a couple of notes for dynamic_bitset. Would next week be too
>> late to post them here? That's, likely, no sooner than Wednesday.
> 
> In addition to the other email? Anyway, next week's fine. The deadline
> is the release. Although it can still be changed afterwards, it's just
> a bit annoying for anyone who's subscribed to the RSS feed.

Odd... the other mail was sent almost 24 hours before the second one; I
thought it had gone into the outer space (the more so because I had just
subscribed to the documentation list). It seems instead that, as soon as
I made another post, it "unblocked" :-) Well, I realized that it would
be good to clarify (in the docs) a couple of details related to library
issue 438; and that, accordingly, the release notices might need a
tweak, too. That's why I thought to postpone everything to next week.

Thanks,
--

-- 
Genny
Permalink | Reply |

Gmane