[1.36.0 beta] Beta release available on SourceForge
New libraries: Accumulators, Exception, Units, Unordered. Updated Libraries: Assign, Foreach, Interprocess, Intrusive, Math, Multi-index Containers, PtrContainer, Spirit, Thread, Xpressive, plus a bunch more. Many thanks to Daniel James, Rene Rivera, Marshall Clow, Eric Niebler, the testers, and all the others who helped to get this beta release together. The beta period will be approximately one week. Please post bug reports here, but also let us hear about success stories too! --Beman
Is thee a link available I carn't find this on source forge. Sean. -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Beman Dawes Sent: 31 July 2008 21:20 To: Boost Developers Mailing List; Boost Users mailing list Subject: [Boost-users] [1.36.0 beta] Beta release available on SourceForge New libraries: Accumulators, Exception, Units, Unordered. Updated Libraries: Assign, Foreach, Interprocess, Intrusive, Math, Multi-index Containers, PtrContainer, Spirit, Thread, Xpressive, plus a bunch more. Many thanks to Daniel James, Rene Rivera, Marshall Clow, Eric Niebler, the testers, and all the others who helped to get this beta release together. The beta period will be approximately one week. Please post bug reports here, but also let us hear about success stories too! --Beman _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users __________ Information from ESET NOD32 Antivirus, version of virus signature database 3315 (20080731) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 3315 (20080731) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
2008/7/31 Sean Farrow
Is thee a link available I carn't find this on source forge. Sean.
http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=8041&release_id=616969
Chers, How can I find the betas in future?
Sean.
-----Original Message-----
From: boost-users-bounces@lists.boost.org
[mailto:boost-users-bounces@lists.boost.org] On Behalf Of Daniel James
Sent: 31 July 2008 21:53
To: boost-users@lists.boost.org
Subject: Re: [Boost-users] [1.36.0 beta] Beta release available
onSourceForge
2008/7/31 Sean Farrow
Is thee a link available I carn't find this on source forge. Sean.
http://sourceforge.net/project/showfiles.php?group_id=7586&package_id=80 41&release_id=616969 _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users __________ Information from ESET NOD32 Antivirus, version of virus signature database 3315 (20080731) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 3315 (20080731) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
2008/7/31 Sean Farrow
Chers, How can I find the betas in future? Sean.
I just went to list of files on sourceforge: http://sourceforge.net/project/showfiles.php?group_id=7586 If you went there, it might not have been up yet. Daniel
I get a compile error with GCC 4.3.1:
/opt2/linux/x86_64/include/boost-1_36/boost/date_time/tz_db_base.hpp:161:
error: declaration of 'typedef class
boost::date_time::dst_adjustment_offsets<typename
time_zone_type::time_duration_type>
boost::date_time::tz_db_base
On Thursday 31 July 2008, Lothar Werzinger wrote:
I get a compile error with GCC 4.3.1:
/opt2/linux/x86_64/include/boost-1_36/boost/date_time/tz_db_base.hpp:161: error: declaration of 'typedef class boost::date_time::dst_adjustment_offsets<typename time_zone_type::time_duration_type> boost::date_time::tz_db_base
::dst_adjustment_offsets' /opt2/linux/x86_64/include/boost-1_36/boost/date_time/time_zone_base.hpp:76 : error: changes meaning of 'dst_adjustment_offsets' from 'class boost::date_time::dst_adjustment_offsets<typename time_zone_type::time_duration_type>' [exec] In file included from /opt2/linux/x86_64/include/boost-1_36/boost/date_time/local_time/tz_databas e.hpp:14, [exec] from /opt2/linux/x86_64/include/boost-1_36/boost/date_time/local_time/local_time .hpp:19,
Lothar
The attached patch fixes the problem Lothar -- Lothar Werzinger Dipl.-Ing. Univ. framework & platform architect Tradescape Inc. - Enabling Efficient Digital Marketplaces 1754 Technology Drive, Suite 128 San Jose, CA 95110 web: http://www.tradescape.biz
Lothar Werzinger wrote:
On Thursday 31 July 2008, Lothar Werzinger wrote:
I get a compile error with GCC 4.3.1:
/opt2/linux/x86_64/include/boost-1_36/boost/date_time/tz_db_base.hpp:161: error: declaration of 'typedef class boost::date_time::dst_adjustment_offsets<typename time_zone_type::time_duration_type> boost::date_time::tz_db_base
::dst_adjustment_offsets' /opt2/linux/x86_64/include/boost-1_36/boost/date_time/time_zone_base.hpp:76 : error: changes meaning of 'dst_adjustment_offsets' from 'class boost::date_time::dst_adjustment_offsets<typename time_zone_type::time_duration_type>' [exec] In file included from /opt2/linux/x86_64/include/boost-1_36/boost/date_time/local_time/tz_databas e.hpp:14, [exec] from /opt2/linux/x86_64/include/boost-1_36/boost/date_time/local_time/local_time .hpp:19,
Lothar
The attached patch fixes the problem
Thanks for the report and patch. I've forwarded it to Jeff Garland. --Beman
Hi there, I can confirm that this fixes the date_time problem in my environment - OpenSUSE 11, 64 bit, g++ 4.3.1 . Best, Ruediger Lothar Werzinger wrote:
On Thursday 31 July 2008, Lothar Werzinger wrote:
I get a compile error with GCC 4.3.1:
/opt2/linux/x86_64/include/boost-1_36/boost/date_time/tz_db_base.hpp:161: error: declaration of 'typedef class boost::date_time::dst_adjustment_offsets<typename time_zone_type::time_duration_type> boost::date_time::tz_db_base
::dst_adjustment_offsets' /opt2/linux/x86_64/include/boost-1_36/boost/date_time/time_zone_base.hpp:76 : error: changes meaning of 'dst_adjustment_offsets' from 'class boost::date_time::dst_adjustment_offsets<typename time_zone_type::time_duration_type>' [exec] In file included from /opt2/linux/x86_64/include/boost-1_36/boost/date_time/local_time/tz_databas e.hpp:14, [exec] from /opt2/linux/x86_64/include/boost-1_36/boost/date_time/local_time/local_time .hpp:19,
Lothar
The attached patch fixes the problem
Lothar
There is a bug in the datetime library iostream operators
$ /opt2/linux/ix86/bin/g++-4.3.1 -I/opt2/linux/x86_64/include/boost-1_36 -o
boost1 boost1.cpp; ./boost1; ./boost1 1; ./boost1 1 2; ./boost1 1 2 3
testing testInputIso ...
expected=2005
actual =2005
expected=Sep
actual =Sep
expected=30
actual =30
expected=18
actual =19
boost1: boost1.cpp:97: void testInputIso(): Assertion
`(static_cast
AMDG Lothar Werzinger wrote:
There is a bug in the datetime library iostream operators
So, why exactly is it a bug for "2005-09-30 19:25:17+01:00" to yield 19 in the hours? What am I missing? In Christ, Steven Watanabe
On Thursday 31 July 2008, Steven Watanabe wrote:
AMDG
Lothar Werzinger wrote:
There is a bug in the datetime library iostream operators
So, why exactly is it a bug for "2005-09-30 19:25:17+01:00" to yield 19 in the hours? What am I missing?
Oops that's a leftover from an earlier try. I wanted to find out if the local or utc time get's returned. Of course the checks should be the same as in InputIsoWide (fixed file is attached) as you can see only the ouputIso works without problems. $ /opt2/linux/ix86/bin/g++-4.3.1 -I/opt2/linux/x86_64/include/boost-1_36 -o boost1 boost1.cpp; ./boost1; ./boost1 1; ./boost1 1 2; ./boost1 1 2 3 testing testInputIso ... expected=2005 actual =2005 expected=Sep actual =Sep expected=30 actual =30 expected=19 actual =19 expected=25 actual =25 expected=17 actual =17 expected=1 actual =0 boost1: boost1.cpp:100: void testInputIso(): Assertion `(true) == (0 != ldt.zone().get())' failed. Aborted testing testInputIsoWide ... expected=2005 terminate called after throwing an instance of 'boost::gregorian::bad_year' what(): Year is out of valid range: 1400..10000 Aborted testing testOutputIso ... expected=2005-09-30 19:25:17+01:00 actual =2005-09-30 19:25:17+01:00 expected=2005-09-30 19:25:17-08:00 actual =2005-09-30 19:25:17-08:00 testing testOutputIso OK testing testOutputIsoWide ... expected=2005-09-30 19:25:17+01:00 actual =2005-Sep-30 19:25:17 CET boost1: boost1.cpp:267: void testOutputIsoWide(): Assertion `(iso8859_1std::string(str)) == (iso8859_1std::string(ss.str()))' failed. Aborted Lothar -- Lothar Werzinger Dipl.-Ing. Univ. framework & platform architect Tradescape Inc. - Enabling Efficient Digital Marketplaces 1754 Technology Drive, Suite 128 San Jose, CA 95110 web: http://www.tradescape.biz
On Thursday 31 July 2008, Lothar Werzinger wrote:
On Thursday 31 July 2008, Steven Watanabe wrote:
AMDG
Lothar Werzinger wrote:
There is a bug in the datetime library iostream operators
So, why exactly is it a bug for "2005-09-30 19:25:17+01:00" to yield 19 in the hours? What am I missing?
Oops that's a leftover from an earlier try. I wanted to find out if the local or utc time get's returned. Of course the checks should be the same as in InputIsoWide (fixed file is attached)
Actually the "fix" is wrong. I let me trick by your question about the 19 in
the hour field. Of course it must be 18 (as it is the UTC time hour field).
The problem stems from the fact that the library fails to parse the offset
and does not create a timezone object. Find the correct test attached.
As stated before I want to read back a time created by the library (and
verified OK by the testOutput* functions). If I am doing something wrong
trying to read it back, please let me know. If this is a "real" bug, please
help to find a fix for the upcoming 1.36 release.
$ /opt2/linux/ix86/bin/g++-4.3.1 -I/opt2/linux/x86_64/include/boost-1_36 -o
boost1 boost1.cpp && (./boost1; ./boost1 1; ./boost1 1 2; ./boost1 1 2 3)
testing testInputIso ...
expected=18
actual =19
boost1: boost1.cpp:103: void testInputIso(): Assertion
`(static_cast
The constructor of local_date_time also behaves strangely, too: according to the documentation the constructor that takes a posix_time::ptime
The given time is expected to be UTC. Therefore, the given time will be adjusted according to the offset described in the time zone.
As you can see in the attached test the constructed local_date_time formats
correctly when printed but provides a wrong local time when the fields are
accessed.
$ /opt2/linux/ix86/bin/g++-4.3.1 -I/opt2/linux/x86_64/include/boost-1_36 -o
boost1 boost1.cpp && (./boost1; ./boost1 1; ./boost1 1 2; ./boost1 1 2 3)
testing testConstructor ...
expected=19
actual =18
boost1: boost1.cpp:110: void testConstructor(): Assertion
`(static_cast
The following compiler warnings in the date_time library can be removed with
the attached patch
[exec] /opt2/linux/x86_64/include/boost-1_36/boost/date_time/time.hpp: In
instantiation of 'std::string boost::date_time::base_time
]':
[exec] /opt2/linux/x86_64/include/boost-1_36/boost/date_time/time_facet.hpp:263:
instantiated from 'OutItrT boost::date_time::time_facet
]':
[exec] /opt2/linux/x86_64/include/boost-1_36/boost/date_time/time_facet.hpp:277:
instantiated from 'OutItrT boost::date_time::time_facet
participants (6)
-
Beman Dawes
-
Daniel James
-
Lothar Werzinger
-
Ruediger Berlich
-
Sean Farrow
-
Steven Watanabe