June 2014 - Boost-users - lists.preview.boost.org

Unexpected behavior when using as::ftime() of Boost Locale library
by Mouse Beer 27 Jun '14

27 Jun '14

Hi all, I see a mismatch when using %Y format specifier with as::ftime. It looks like it outputs the year according to the week of the year. I hope I didn't miss or misunderstand anything... please find my small test program attached for reference. It was compiled as follows: g++ -g -Wall -I /opt/boost/1.55/include -L /opt/boost/1.55/lib -lboost_locale -lboost_thread -lboost_system -licuuc -licui18n -licudata -lpthread -lrt boost_dates_test.cpp I am running on Debian Testing: $ ldd a.out linux-vdso.so.1 (0x00007fffa39fe000) libboost_locale.so.1.55.0 => /opt/boost/1.55/lib/libboost_locale.so.1.55.0 (0x00007fba3335b000) libboost_thread.so.1.55.0 => /opt/boost/1.55/lib/libboost_thread.so.1.55.0 (0x00007fba33142000) libboost_system.so.1.55.0 => /opt/boost/1.55/lib/libboost_system.so.1.55.0 (0x00007fba32f3e000) libicuuc.so.52 => /usr/lib/x86_64-linux-gnu/libicuuc.so.52 (0x00007fba32ba2000) libicui18n.so.52 => /usr/lib/x86_64-linux-gnu/libicui18n.so.52 (0x00007fba3279a000) libicudata.so.52 => /usr/lib/x86_64-linux-gnu/libicudata.so.52 (0x00007fba30f2c000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fba30d0f000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fba30b07000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fba307fb000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fba304fa000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fba302e4000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fba2ff3a000) libboost_chrono.so.1.55.0 => /opt/boost/1.55/lib/libboost_chrono.so.1.55.0 (0x00007fba2fd34000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fba2fb2f000) /lib64/ld-linux-x86-64.so.2 (0x00007fba33642000) The program shows the output of cout<<date_time and cout<<as:ftime("%Y-%m...")<<date_time If a mismatch in the year is detected, a "!" is added at the end of the line. When running with en_US locale, the output is as follows: [ 10:49:40 ] [0] $ export LC_ALL=en_US.utf8 [ 10:50:39 ] [0] $ locale LANG= LANGUAGE= LC_CTYPE="en_US.utf8" LC_NUMERIC="en_US.utf8" LC_TIME="en_US.utf8" LC_COLLATE="en_US.utf8" LC_MONETARY="en_US.utf8" LC_MESSAGES="en_US.utf8" LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL=en_US.utf8 [ 10:50:41 ] [0] $ ./a.out Dec 27, 2000, 12:00:00 AM ++ 2000-12-27 00:00:00 Dec 28, 2000, 12:00:00 AM ++ 2000-12-28 00:00:00 Dec 29, 2000, 12:00:00 AM ++ 2000-12-29 00:00:00 Dec 30, 2000, 12:00:00 AM ++ 2000-12-30 00:00:00 Dec 31, 2000, 12:00:00 AM ++ 2001-12-31 00:00:00 ! Jan 1, 2001, 12:00:00 AM ++ 2001-01-01 00:00:00 Jan 2, 2001, 12:00:00 AM ++ 2001-01-02 00:00:00 Jan 3, 2001, 12:00:00 AM ++ 2001-01-03 00:00:00 Jan 4, 2001, 12:00:00 AM ++ 2001-01-04 00:00:00 Jan 5, 2001, 12:00:00 AM ++ 2001-01-05 00:00:00 Dec 27, 2001, 12:00:00 AM ++ 2001-12-27 00:00:00 Dec 28, 2001, 12:00:00 AM ++ 2001-12-28 00:00:00 Dec 29, 2001, 12:00:00 AM ++ 2001-12-29 00:00:00 Dec 30, 2001, 12:00:00 AM ++ 2002-12-30 00:00:00 ! Dec 31, 2001, 12:00:00 AM ++ 2002-12-31 00:00:00 ! Jan 1, 2002, 12:00:00 AM ++ 2002-01-01 00:00:00 Jan 2, 2002, 12:00:00 AM ++ 2002-01-02 00:00:00 Jan 3, 2002, 12:00:00 AM ++ 2002-01-03 00:00:00 Jan 4, 2002, 12:00:00 AM ++ 2002-01-04 00:00:00 Jan 5, 2002, 12:00:00 AM ++ 2002-01-05 00:00:00 Dec 27, 2002, 12:00:00 AM ++ 2002-12-27 00:00:00 Dec 28, 2002, 12:00:00 AM ++ 2002-12-28 00:00:00 Dec 29, 2002, 12:00:00 AM ++ 2003-12-29 00:00:00 ! Dec 30, 2002, 12:00:00 AM ++ 2003-12-30 00:00:00 ! Dec 31, 2002, 12:00:00 AM ++ 2003-12-31 00:00:00 ! Jan 1, 2003, 12:00:00 AM ++ 2003-01-01 00:00:00 Jan 2, 2003, 12:00:00 AM ++ 2003-01-02 00:00:00 Jan 3, 2003, 12:00:00 AM ++ 2003-01-03 00:00:00 Jan 4, 2003, 12:00:00 AM ++ 2003-01-04 00:00:00 Jan 5, 2003, 12:00:00 AM ++ 2003-01-05 00:00:00 Dec 27, 2003, 12:00:00 AM ++ 2003-12-27 00:00:00 Dec 28, 2003, 12:00:00 AM ++ 2004-12-28 00:00:00 ! Dec 29, 2003, 12:00:00 AM ++ 2004-12-29 00:00:00 ! Dec 30, 2003, 12:00:00 AM ++ 2004-12-30 00:00:00 ! Dec 31, 2003, 12:00:00 AM ++ 2004-12-31 00:00:00 ! Jan 1, 2004, 12:00:00 AM ++ 2004-01-01 00:00:00 Jan 2, 2004, 12:00:00 AM ++ 2004-01-02 00:00:00 Jan 3, 2004, 12:00:00 AM ++ 2004-01-03 00:00:00 Jan 4, 2004, 12:00:00 AM ++ 2004-01-04 00:00:00 Jan 5, 2004, 12:00:00 AM ++ 2004-01-05 00:00:00 Dec 27, 2004, 12:00:00 AM ++ 2005-12-27 00:00:00 ! Dec 28, 2004, 12:00:00 AM ++ 2005-12-28 00:00:00 ! Dec 29, 2004, 12:00:00 AM ++ 2005-12-29 00:00:00 ! Dec 30, 2004, 12:00:00 AM ++ 2005-12-30 00:00:00 ! Dec 31, 2004, 12:00:00 AM ++ 2005-12-31 00:00:00 ! Jan 1, 2005, 12:00:00 AM ++ 2005-01-01 00:00:00 Jan 2, 2005, 12:00:00 AM ++ 2005-01-02 00:00:00 Jan 3, 2005, 12:00:00 AM ++ 2005-01-03 00:00:00 Jan 4, 2005, 12:00:00 AM ++ 2005-01-04 00:00:00 Jan 5, 2005, 12:00:00 AM ++ 2005-01-05 00:00:00 Dec 27, 2005, 12:00:00 AM ++ 2005-12-27 00:00:00 Dec 28, 2005, 12:00:00 AM ++ 2005-12-28 00:00:00 Dec 29, 2005, 12:00:00 AM ++ 2005-12-29 00:00:00 Dec 30, 2005, 12:00:00 AM ++ 2005-12-30 00:00:00 Dec 31, 2005, 12:00:00 AM ++ 2005-12-31 00:00:00 Jan 1, 2006, 12:00:00 AM ++ 2006-01-01 00:00:00 Jan 2, 2006, 12:00:00 AM ++ 2006-01-02 00:00:00 Jan 3, 2006, 12:00:00 AM ++ 2006-01-03 00:00:00 Jan 4, 2006, 12:00:00 AM ++ 2006-01-04 00:00:00 Jan 5, 2006, 12:00:00 AM ++ 2006-01-05 00:00:00 Dec 27, 2006, 12:00:00 AM ++ 2006-12-27 00:00:00 Dec 28, 2006, 12:00:00 AM ++ 2006-12-28 00:00:00 Dec 29, 2006, 12:00:00 AM ++ 2006-12-29 00:00:00 Dec 30, 2006, 12:00:00 AM ++ 2006-12-30 00:00:00 Dec 31, 2006, 12:00:00 AM ++ 2007-12-31 00:00:00 ! Jan 1, 2007, 12:00:00 AM ++ 2007-01-01 00:00:00 Jan 2, 2007, 12:00:00 AM ++ 2007-01-02 00:00:00 Jan 3, 2007, 12:00:00 AM ++ 2007-01-03 00:00:00 Jan 4, 2007, 12:00:00 AM ++ 2007-01-04 00:00:00 Jan 5, 2007, 12:00:00 AM ++ 2007-01-05 00:00:00 Dec 27, 2007, 12:00:00 AM ++ 2007-12-27 00:00:00 Dec 28, 2007, 12:00:00 AM ++ 2007-12-28 00:00:00 Dec 29, 2007, 12:00:00 AM ++ 2007-12-29 00:00:00 Dec 30, 2007, 12:00:00 AM ++ 2008-12-30 00:00:00 ! Dec 31, 2007, 12:00:00 AM ++ 2008-12-31 00:00:00 ! Jan 1, 2008, 12:00:00 AM ++ 2008-01-01 00:00:00 Jan 2, 2008, 12:00:00 AM ++ 2008-01-02 00:00:00 Jan 3, 2008, 12:00:00 AM ++ 2008-01-03 00:00:00 Jan 4, 2008, 12:00:00 AM ++ 2008-01-04 00:00:00 Jan 5, 2008, 12:00:00 AM ++ 2008-01-05 00:00:00 Dec 27, 2008, 12:00:00 AM ++ 2008-12-27 00:00:00 Dec 28, 2008, 12:00:00 AM ++ 2009-12-28 00:00:00 ! Dec 29, 2008, 12:00:00 AM ++ 2009-12-29 00:00:00 ! Dec 30, 2008, 12:00:00 AM ++ 2009-12-30 00:00:00 ! Dec 31, 2008, 12:00:00 AM ++ 2009-12-31 00:00:00 ! Jan 1, 2009, 12:00:00 AM ++ 2009-01-01 00:00:00 Jan 2, 2009, 12:00:00 AM ++ 2009-01-02 00:00:00 Jan 3, 2009, 12:00:00 AM ++ 2009-01-03 00:00:00 Jan 4, 2009, 12:00:00 AM ++ 2009-01-04 00:00:00 Jan 5, 2009, 12:00:00 AM ++ 2009-01-05 00:00:00 Dec 27, 2009, 12:00:00 AM ++ 2010-12-27 00:00:00 ! Dec 28, 2009, 12:00:00 AM ++ 2010-12-28 00:00:00 ! Dec 29, 2009, 12:00:00 AM ++ 2010-12-29 00:00:00 ! Dec 30, 2009, 12:00:00 AM ++ 2010-12-30 00:00:00 ! Dec 31, 2009, 12:00:00 AM ++ 2010-12-31 00:00:00 ! Jan 1, 2010, 12:00:00 AM ++ 2010-01-01 00:00:00 Jan 2, 2010, 12:00:00 AM ++ 2010-01-02 00:00:00 Jan 3, 2010, 12:00:00 AM ++ 2010-01-03 00:00:00 Jan 4, 2010, 12:00:00 AM ++ 2010-01-04 00:00:00 Jan 5, 2010, 12:00:00 AM ++ 2010-01-05 00:00:00 Dec 27, 2010, 12:00:00 AM ++ 2011-12-27 00:00:00 ! Dec 28, 2010, 12:00:00 AM ++ 2011-12-28 00:00:00 ! Dec 29, 2010, 12:00:00 AM ++ 2011-12-29 00:00:00 ! Dec 30, 2010, 12:00:00 AM ++ 2011-12-30 00:00:00 ! Dec 31, 2010, 12:00:00 AM ++ 2011-12-31 00:00:00 ! Jan 1, 2011, 12:00:00 AM ++ 2011-01-01 00:00:00 Jan 2, 2011, 12:00:00 AM ++ 2011-01-02 00:00:00 Jan 3, 2011, 12:00:00 AM ++ 2011-01-03 00:00:00 Jan 4, 2011, 12:00:00 AM ++ 2011-01-04 00:00:00 Jan 5, 2011, 12:00:00 AM ++ 2011-01-05 00:00:00 Dec 27, 2011, 12:00:00 AM ++ 2011-12-27 00:00:00 Dec 28, 2011, 12:00:00 AM ++ 2011-12-28 00:00:00 Dec 29, 2011, 12:00:00 AM ++ 2011-12-29 00:00:00 Dec 30, 2011, 12:00:00 AM ++ 2011-12-30 00:00:00 Dec 31, 2011, 12:00:00 AM ++ 2011-12-31 00:00:00 Jan 1, 2012, 12:00:00 AM ++ 2012-01-01 00:00:00 Jan 2, 2012, 12:00:00 AM ++ 2012-01-02 00:00:00 Jan 3, 2012, 12:00:00 AM ++ 2012-01-03 00:00:00 Jan 4, 2012, 12:00:00 AM ++ 2012-01-04 00:00:00 Jan 5, 2012, 12:00:00 AM ++ 2012-01-05 00:00:00 Dec 27, 2012, 12:00:00 AM ++ 2012-12-27 00:00:00 Dec 28, 2012, 12:00:00 AM ++ 2012-12-28 00:00:00 Dec 29, 2012, 12:00:00 AM ++ 2012-12-29 00:00:00 Dec 30, 2012, 12:00:00 AM ++ 2013-12-30 00:00:00 ! Dec 31, 2012, 12:00:00 AM ++ 2013-12-31 00:00:00 ! Jan 1, 2013, 12:00:00 AM ++ 2013-01-01 00:00:00 Jan 2, 2013, 12:00:00 AM ++ 2013-01-02 00:00:00 Jan 3, 2013, 12:00:00 AM ++ 2013-01-03 00:00:00 Jan 4, 2013, 12:00:00 AM ++ 2013-01-04 00:00:00 Jan 5, 2013, 12:00:00 AM ++ 2013-01-05 00:00:00 Dec 27, 2013, 12:00:00 AM ++ 2013-12-27 00:00:00 Dec 28, 2013, 12:00:00 AM ++ 2013-12-28 00:00:00 Dec 29, 2013, 12:00:00 AM ++ 2014-12-29 00:00:00 ! Dec 30, 2013, 12:00:00 AM ++ 2014-12-30 00:00:00 ! Dec 31, 2013, 12:00:00 AM ++ 2014-12-31 00:00:00 ! Jan 1, 2014, 12:00:00 AM ++ 2014-01-01 00:00:00 Jan 2, 2014, 12:00:00 AM ++ 2014-01-02 00:00:00 Jan 3, 2014, 12:00:00 AM ++ 2014-01-03 00:00:00 Jan 4, 2014, 12:00:00 AM ++ 2014-01-04 00:00:00 Jan 5, 2014, 12:00:00 AM ++ 2014-01-05 00:00:00 When running with de_DE locale, the output is as follows: [ 10:51:42 ] [0] $ export LC_ALL=de_DE.utf8 [ 10:55:04 ] [0] $ locale LANG= LANGUAGE= LC_CTYPE="de_DE.utf8" LC_NUMERIC="de_DE.utf8" LC_TIME="de_DE.utf8" LC_COLLATE="de_DE.utf8" LC_MONETARY="de_DE.utf8" LC_MESSAGES="de_DE.utf8" LC_PAPER="de_DE.utf8" LC_NAME="de_DE.utf8" LC_ADDRESS="de_DE.utf8" LC_TELEPHONE="de_DE.utf8" LC_MEASUREMENT="de_DE.utf8" LC_IDENTIFICATION="de_DE.utf8" LC_ALL=de_DE.utf8 [ 10:55:05 ] [0] $ ./a.out 27.12.2000 00:00:00 ++ 2000-12-27 00:00:00 28.12.2000 00:00:00 ++ 2000-12-28 00:00:00 29.12.2000 00:00:00 ++ 2000-12-29 00:00:00 30.12.2000 00:00:00 ++ 2000-12-30 00:00:00 31.12.2000 00:00:00 ++ 2000-12-31 00:00:00 01.01.2001 00:00:00 ++ 2001-01-01 00:00:00 02.01.2001 00:00:00 ++ 2001-01-02 00:00:00 03.01.2001 00:00:00 ++ 2001-01-03 00:00:00 04.01.2001 00:00:00 ++ 2001-01-04 00:00:00 05.01.2001 00:00:00 ++ 2001-01-05 00:00:00 27.12.2001 00:00:00 ++ 2001-12-27 00:00:00 28.12.2001 00:00:00 ++ 2001-12-28 00:00:00 29.12.2001 00:00:00 ++ 2001-12-29 00:00:00 30.12.2001 00:00:00 ++ 2001-12-30 00:00:00 31.12.2001 00:00:00 ++ 2002-12-31 00:00:00 ! 01.01.2002 00:00:00 ++ 2002-01-01 00:00:00 02.01.2002 00:00:00 ++ 2002-01-02 00:00:00 03.01.2002 00:00:00 ++ 2002-01-03 00:00:00 04.01.2002 00:00:00 ++ 2002-01-04 00:00:00 05.01.2002 00:00:00 ++ 2002-01-05 00:00:00 27.12.2002 00:00:00 ++ 2002-12-27 00:00:00 28.12.2002 00:00:00 ++ 2002-12-28 00:00:00 29.12.2002 00:00:00 ++ 2002-12-29 00:00:00 30.12.2002 00:00:00 ++ 2003-12-30 00:00:00 ! 31.12.2002 00:00:00 ++ 2003-12-31 00:00:00 ! 01.01.2003 00:00:00 ++ 2003-01-01 00:00:00 02.01.2003 00:00:00 ++ 2003-01-02 00:00:00 03.01.2003 00:00:00 ++ 2003-01-03 00:00:00 04.01.2003 00:00:00 ++ 2003-01-04 00:00:00 05.01.2003 00:00:00 ++ 2003-01-05 00:00:00 27.12.2003 00:00:00 ++ 2003-12-27 00:00:00 28.12.2003 00:00:00 ++ 2003-12-28 00:00:00 29.12.2003 00:00:00 ++ 2004-12-29 00:00:00 ! 30.12.2003 00:00:00 ++ 2004-12-30 00:00:00 ! 31.12.2003 00:00:00 ++ 2004-12-31 00:00:00 ! 01.01.2004 00:00:00 ++ 2004-01-01 00:00:00 02.01.2004 00:00:00 ++ 2004-01-02 00:00:00 03.01.2004 00:00:00 ++ 2004-01-03 00:00:00 04.01.2004 00:00:00 ++ 2004-01-04 00:00:00 05.01.2004 00:00:00 ++ 2004-01-05 00:00:00 27.12.2004 00:00:00 ++ 2004-12-27 00:00:00 28.12.2004 00:00:00 ++ 2004-12-28 00:00:00 29.12.2004 00:00:00 ++ 2004-12-29 00:00:00 30.12.2004 00:00:00 ++ 2004-12-30 00:00:00 31.12.2004 00:00:00 ++ 2004-12-31 00:00:00 01.01.2005 00:00:00 ++ 2004-01-01 00:00:00 ! 02.01.2005 00:00:00 ++ 2004-01-02 00:00:00 ! 03.01.2005 00:00:00 ++ 2005-01-03 00:00:00 04.01.2005 00:00:00 ++ 2005-01-04 00:00:00 05.01.2005 00:00:00 ++ 2005-01-05 00:00:00 27.12.2005 00:00:00 ++ 2005-12-27 00:00:00 28.12.2005 00:00:00 ++ 2005-12-28 00:00:00 29.12.2005 00:00:00 ++ 2005-12-29 00:00:00 30.12.2005 00:00:00 ++ 2005-12-30 00:00:00 31.12.2005 00:00:00 ++ 2005-12-31 00:00:00 01.01.2006 00:00:00 ++ 2005-01-01 00:00:00 ! 02.01.2006 00:00:00 ++ 2006-01-02 00:00:00 03.01.2006 00:00:00 ++ 2006-01-03 00:00:00 04.01.2006 00:00:00 ++ 2006-01-04 00:00:00 05.01.2006 00:00:00 ++ 2006-01-05 00:00:00 27.12.2006 00:00:00 ++ 2006-12-27 00:00:00 28.12.2006 00:00:00 ++ 2006-12-28 00:00:00 29.12.2006 00:00:00 ++ 2006-12-29 00:00:00 30.12.2006 00:00:00 ++ 2006-12-30 00:00:00 31.12.2006 00:00:00 ++ 2006-12-31 00:00:00 01.01.2007 00:00:00 ++ 2007-01-01 00:00:00 02.01.2007 00:00:00 ++ 2007-01-02 00:00:00 03.01.2007 00:00:00 ++ 2007-01-03 00:00:00 04.01.2007 00:00:00 ++ 2007-01-04 00:00:00 05.01.2007 00:00:00 ++ 2007-01-05 00:00:00 27.12.2007 00:00:00 ++ 2007-12-27 00:00:00 28.12.2007 00:00:00 ++ 2007-12-28 00:00:00 29.12.2007 00:00:00 ++ 2007-12-29 00:00:00 30.12.2007 00:00:00 ++ 2007-12-30 00:00:00 31.12.2007 00:00:00 ++ 2008-12-31 00:00:00 ! 01.01.2008 00:00:00 ++ 2008-01-01 00:00:00 02.01.2008 00:00:00 ++ 2008-01-02 00:00:00 03.01.2008 00:00:00 ++ 2008-01-03 00:00:00 04.01.2008 00:00:00 ++ 2008-01-04 00:00:00 05.01.2008 00:00:00 ++ 2008-01-05 00:00:00 27.12.2008 00:00:00 ++ 2008-12-27 00:00:00 28.12.2008 00:00:00 ++ 2008-12-28 00:00:00 29.12.2008 00:00:00 ++ 2009-12-29 00:00:00 ! 30.12.2008 00:00:00 ++ 2009-12-30 00:00:00 ! 31.12.2008 00:00:00 ++ 2009-12-31 00:00:00 ! 01.01.2009 00:00:00 ++ 2009-01-01 00:00:00 02.01.2009 00:00:00 ++ 2009-01-02 00:00:00 03.01.2009 00:00:00 ++ 2009-01-03 00:00:00 04.01.2009 00:00:00 ++ 2009-01-04 00:00:00 05.01.2009 00:00:00 ++ 2009-01-05 00:00:00 27.12.2009 00:00:00 ++ 2009-12-27 00:00:00 28.12.2009 00:00:00 ++ 2009-12-28 00:00:00 29.12.2009 00:00:00 ++ 2009-12-29 00:00:00 30.12.2009 00:00:00 ++ 2009-12-30 00:00:00 31.12.2009 00:00:00 ++ 2009-12-31 00:00:00 01.01.2010 00:00:00 ++ 2009-01-01 00:00:00 ! 02.01.2010 00:00:00 ++ 2009-01-02 00:00:00 ! 03.01.2010 00:00:00 ++ 2009-01-03 00:00:00 ! 04.01.2010 00:00:00 ++ 2010-01-04 00:00:00 05.01.2010 00:00:00 ++ 2010-01-05 00:00:00 27.12.2010 00:00:00 ++ 2010-12-27 00:00:00 28.12.2010 00:00:00 ++ 2010-12-28 00:00:00 29.12.2010 00:00:00 ++ 2010-12-29 00:00:00 30.12.2010 00:00:00 ++ 2010-12-30 00:00:00 31.12.2010 00:00:00 ++ 2010-12-31 00:00:00 01.01.2011 00:00:00 ++ 2010-01-01 00:00:00 ! 02.01.2011 00:00:00 ++ 2010-01-02 00:00:00 ! 03.01.2011 00:00:00 ++ 2011-01-03 00:00:00 04.01.2011 00:00:00 ++ 2011-01-04 00:00:00 05.01.2011 00:00:00 ++ 2011-01-05 00:00:00 27.12.2011 00:00:00 ++ 2011-12-27 00:00:00 28.12.2011 00:00:00 ++ 2011-12-28 00:00:00 29.12.2011 00:00:00 ++ 2011-12-29 00:00:00 30.12.2011 00:00:00 ++ 2011-12-30 00:00:00 31.12.2011 00:00:00 ++ 2011-12-31 00:00:00 01.01.2012 00:00:00 ++ 2011-01-01 00:00:00 ! 02.01.2012 00:00:00 ++ 2012-01-02 00:00:00 03.01.2012 00:00:00 ++ 2012-01-03 00:00:00 04.01.2012 00:00:00 ++ 2012-01-04 00:00:00 05.01.2012 00:00:00 ++ 2012-01-05 00:00:00 27.12.2012 00:00:00 ++ 2012-12-27 00:00:00 28.12.2012 00:00:00 ++ 2012-12-28 00:00:00 29.12.2012 00:00:00 ++ 2012-12-29 00:00:00 30.12.2012 00:00:00 ++ 2012-12-30 00:00:00 31.12.2012 00:00:00 ++ 2013-12-31 00:00:00 ! 01.01.2013 00:00:00 ++ 2013-01-01 00:00:00 02.01.2013 00:00:00 ++ 2013-01-02 00:00:00 03.01.2013 00:00:00 ++ 2013-01-03 00:00:00 04.01.2013 00:00:00 ++ 2013-01-04 00:00:00 05.01.2013 00:00:00 ++ 2013-01-05 00:00:00 27.12.2013 00:00:00 ++ 2013-12-27 00:00:00 28.12.2013 00:00:00 ++ 2013-12-28 00:00:00 29.12.2013 00:00:00 ++ 2013-12-29 00:00:00 30.12.2013 00:00:00 ++ 2014-12-30 00:00:00 ! 31.12.2013 00:00:00 ++ 2014-12-31 00:00:00 ! 01.01.2014 00:00:00 ++ 2014-01-01 00:00:00 02.01.2014 00:00:00 ++ 2014-01-02 00:00:00 03.01.2014 00:00:00 ++ 2014-01-03 00:00:00 04.01.2014 00:00:00 ++ 2014-01-04 00:00:00 05.01.2014 00:00:00 ++ 2014-01-05 00:00:00 Sorry for the long post! Did I make any mistake in my program or is this a bug of as::ftime("%Y") formatting? Thank you yery much for your help! Regards, Holger

1 0

[Boost : icpc assignment operator compiler error with boost filter_iterator and filtered_graph
by Aniket Pugaonkar 26 Jun '14

26 Jun '14

Hello, I have the following filter iterator working perfectly with gcc 4.7 and 4.9 as well (C++11 support) But when I compile my code with intel compiler 13.0.1 version I get the following error error: *implicitly generated assignment operator cannot copy: reference member* "my_func::G" ... Details: I am using a filtered_graph over Boost::adjacency_list as my graph type (Graph_t). The vertex_iterator (from graph_traits<Graph_t> .. provides iterator range to iterate over graph vertices. I have to assign each graph vertex an id (using property_maps) and group them together by applying filter_iterator over vertex iterator. example: suppose I want to create 4 subgroups of vertices. So I create a filter predicate which is passed to filter iterator which gives me iterators <fbegin, fend> satisfying the predicate. For FOUR such groups, I get 4 pairs of filter iterators. A vector stores such filter_iterator pairs. std::vector < pair <filter_iterator_t, filter_iterator_t> > my_vector //stores iterator pair. Here is the code: vertex_iterator vbegin, vend; boost::tie(vbegin, vend) = boost::vertices(G); for (int i=0; i<4; ++i) { //for each i, create a filter_pred object my_filter_pred <Graph> filter_pred(G, i) //now create begin and end filter iterators as follows auto fbegin = boost::make_filter_iterator< my_filter_pred<Graph>, vertex_iterator> (filter_pred, vbegin, vend) auto fend = boost::make_filter_iterator< my_filter_pred<Graph>, vertex_iterator> (filter_pred, vend, vend) //fbegin, fend are of type filter iterator //insert the iterator pair into vector my_vector.push_back( std::make_pair (fbegin, fend) ); } The predicate is below : template<typename Graph> struct my_filter_pred { public: my_filter_pred() { } my_filter_pred(Graph& _G, int _value) : G(_G), value(_value) { } template<typename vertex_t> bool operator() (vertex_t vertex) { //get property "p" of vertex in graph G auto p = get (mypropertytype, vertex, G); return (p.val == value); } private: Graph& G; } ERROR : error: implicitly generated assignment operator cannot copy: reference member "my_filter_pred <Graph>::G [with ... ]" I tried to provide my own assignment operator as below: my_filter_pred& operator=(const my_filter_pred& other) { if (this != &other) G = other.G; return *this; } But it gave the same icpc error for actual typedef graph which is below : error: implicitly generated assignment operator cannot copy: " implicit generation of boost::filtered_graph_base<Graph_t> " .... Please help what should I do in this case to work. main motive : is to have a container which stores <iterator, iterator> pair which satisfies a predicate. Filter iterator was the best choice i could have to apply different filter predicate to same vertex_iterator range vbegin, vend; Thanks Aniket Pugaonkar Aniket Pugaonkar

1 0

[Bimap] Iterator invalidation
by Adam Badura 25 Jun '14

25 Jun '14

What are rules for iterator invalidation in Boost.Bimap? I have looked in documentation (version 1.55) but didn't found anything. I'm particularly interested in the bimap<...>::iterator (or ::const_iterator) invalidation. But the question remains valid for any kind of iterators. Adam Badura

2 2

Autobahn for C++: RPC and PubSub
by Tobias Oberstein 24 Jun '14

24 Jun '14

Hi, I'm happy to anounce Autobahn|Cpp - another subproject of Autobahn (http://autobahn.ws) this time for C++ 11 / Boost. Autobahn|Cpp allows remote procedure calls and publish & subscribe messaging for C++ application components and uses boost::future, continuations and Boost/ASIO as underlying network library. Here is how app code looks like: https://github.com/tavendo/AutobahnCpp/blob/master/README.md#show-me-some-c… Using Autobahn|Cpp, you can e.g. call your C++ code from JavaScript running in a browser. And much more. This is an early alpha version, things aren't fully hashed out, but there are a couple of examples included here: https://github.com/tavendo/AutobahnCpp/blob/master/README.md#examples Cheers, /Tobias

2 3

Boost Social Event at CppCon
by Jon Kalb 24 Jun '14

24 Jun '14

Boosters, Because a lot of Boosters are going to be attending CppCon, we¹d like to arrange a social event for Boosters/C++Now regulars. http://cppcon.org/ If you are planning to attend CppCon or even If you are just going to be in or around Bellevue, Washington between September 7th and 12 and you¹d like to join us for dinner, please let us know so we can get a count. Please send mail to: social(a)boost.org Once we settle on a date, etc, we¹ll let everyone who responded know when and where, so please let us know, even if you are a ³maybe.² This year¹s CppCon program includes sessions from a number of Boosters and C++Now regulars with sessions specifically about Boost Libraries. If you are considering attending, please be aware that the Early Bird registration deadline is just days away. http://cppcon.org/registration/ If you are attending, please make your hotel reservations soon. We are likely to sell out of our room block. http://cppcon.org/lodging/ I hope to see you at CppCon. Jon

1 0

Re: [Boost-users] [Boost.Test] BOOST_CHECK_THROW behaviour
by Ghyslain Leclerc 23 Jun '14

23 Jun '14

On 23/06/2014 17:19:01 +1200, Gavin Lambert wrote >>You could try submitting that as a bug report in Trac (if it's not already there), or waiting for Gennadiy Rozental's response. Done. I hope I did it properly. Never reported a bug on Boost before. Quoted our discussion, so that some more info is available if necessary. >>In the meantime, you'd need to write a more intelligent test yourself. I will do it manually. Found someone on Stack Overflow who wanted the same behavior I expected and did it. In case it helps someone, here is the snippet: try { … code that should throw ... BOOST_ERROR( “<function_name> did not throw anything. Expected a <exception_name>” ); } catch( <exception_name> const& ) { //ok, this is the expected case } catch(…) { BOOST_ERROR( “<function_name> has throw an unknown exception, but a <exception_name> was expected.” ); } and the reference: http://stackoverflow.com/questions/21774387/boost-unit-testing-exceptions Thanks again for your help.

1 0

[Boost.Test] BOOST_CHECK_THROW behaviour
by Ghyslain Leclerc 23 Jun '14

23 Jun '14

Hello, Sorry for the long post! I have a simple class, which I am posting a fraction of here for discussion sake: ------------------------------------------------------ class AsciiTableRow { public: void setCol( std::size_t colIdx, std::string const& newContent ); void setCol( std::size_t colIdx, const char* newContent ); private: void checkIdxBound_( std::size_t colIdx, std::string const& msg ); std::vector< std::string > data_; bool maxColWidthIsValid_; } inline void AsciiTableRow::setCol( std::size_t colIdx, std::string const& newVal ) { checkIdxBound_( colIdx, "setCol" ); maxColWidthIsValid_ = false; data_[colIdx] = newVal; } inline void AsciiTableRow::setCol( std::size_t colIdx, const char* newContent ) { setCol( colIdx, std::string( newContent ) ); } inline void AsciiTableRow::checkIdxBound_( std::size_t colIdx, std::string const& msg ) { if( colIdx > data_.size() ) { throw std::out_of_range( "AsciiTableRow::" + msg + " : colIdx out of range" ); } } ------------------------------------------------------ The code above should be sufficient for the discussion and I don’t think any other code is relevant. Should you need to see my constructor and destructor, nothing is virtual so I just copy every value and set some defaults. Nothing fancy, but I will gladly post the code if need be. What I do then is try and devise a test to see if the exception is indeed thrown and if it is the correct one. Here is the code I use: AsciiTableRow testRow; // empty, so any index will throw BOOST_CHECK_THROW( testRow.setCol( 30, 12 ), std::out_of_range ); BOOST_CHECK_THROW( testRow.setCol( 30, 12l ), std::out_of_range ); This works fine. Then, I had the idea to check what the behaviour would be if the wrong exception is thrown. I simply changed the first call like this : BOOST_CHECK_THROW( testRow.setCol( 30, 12 ), std::runtime_error ); BOOST_CHECK_THROW( testRow.setCol( 30, 12l ), std::out_of_range ); I was under the impression (and I might be wrong here, sorry :-( ) that the Boost.Test library would (the numbers are not to mean that order, simply there for enumeration): 1- output a message saying the test has failed, that an exception was indeed thrown, but it was not a runtime_error 2- continue the rest of the test (single test currently) 3- terminate but I actually never get the message of step 1, the execution of the rest of the test seems never occur (the second BOOST_CHECK_THROW) and the program terminate because of my exception and not very gracefully. I guess my questions to the other users here are: - Was my understanding of what BOOST_CHECK_THROW does flawed ? - Is the behaviour normal ? - Is there an obvious problem I am missing with the design of my simple class ? In case it is useful, I am on OSX 10.9. I have compiled boost myself (sources of version 1.55 downloaded from the Boost site). I compile my work with C++11 enabled. I am using GCC 4.7 installed via Macports. Anyhow, any insight will be appreciated. As everyone is busy, thanks in advance to anybody for any time spent on this. Ghyslain

2 1

[asio] Closing async client socket after writing last message
by Nicholas Yue 23 Jun '14

23 Jun '14

Hi, I have adapted the chat tutorial example to send messages to a similar (chat tutorial based) server. It is currently working fine however due to the async_write(), I can't close the socket until after all the pending data has been processed on the server end. I have google and found discussion and mentioned about async_write() completion handler calling socket.close() however, I was not able to find specific detail as to how that is done. I want to avoid closing the connection prematurely as it is asynchronous writing. My current do_write() looks like this void DisplayChatClient::do_write(DisplayChatMessage msg) { DLOG(INFO) << "DisplayChatClient::do_write()"; bool write_in_progress = !write_msgs_.empty(); write_msgs_.push_back(msg); if (!write_in_progress) { boost::asio::async_write(socket_, boost::asio::buffer(write_msgs_.front().data(), write_msgs_.front().length()), boost::bind(&DisplayChatClient::handle_write, this, boost::asio::placeholders::error)); } } void DisplayChatClient::handle_write(const boost::system::error_code& error) { DLOG(INFO) << "DisplayChatClient::handle_write()"; if (!error) { write_msgs_.pop_front(); if (!write_msgs_.empty()) { boost::asio::async_write(socket_, boost::asio::buffer(write_msgs_.front().data(), write_msgs_.front().length()), boost::bind(&DisplayChatClient::handle_write, this, boost::asio::placeholders::error)); } } else { do_close(); } } Cheers -- Nicholas Yue Graphics - Arnold, Alembic, RenderMan, OpenGL, HDF5 Custom Dev - C++ porting, OSX, Linux, Windows http://au.linkedin.com/in/nicholasyue https://vimeo.com/channels/naiadtools

4 7

Boost Filesystem fails with FreeBSD 10, clang, and boost
by Ricky Huang 21 Jun '14

21 Jun '14

Hello all, I am currently migrating to a FreeBSD 10 system which comes default with clang language. I was able to compile Boost just fine. But when I include filesysstem.hpp to it, I get the following error message: > Linking CXX executable boost_clang_test > /usr/bin/ld: : invalid DSO for symbol `_ZN5boost6system15system_categoryEv' definition > /usr/local/lib/libboost_system.so.1.55.0: could not read symbols: Bad value > CC: error: linker command failed with exit code 1 (use -v to see invocation) > *** Error code 1 > > Stop. I am using cmake as my build system, could it be possible that I need to adjust my cmake variables? I am not sure if I've came to correct forum or should this be on FreeBSD, clang, CMake forum(s)? Please let me know if I am at the wrong place… The minimum amount of code to induce the problem are the following 2 files: CMakeLists.txt: cmake_minimum_required(VERSION 2.8) # Find and include Boost libraries find_package(Boost 1.55 COMPONENTS filesystem REQUIRED) include_directories(${Boost_INCLUDE_DIR}) set(LIBS ${LIBS} ${Boost_LIBRARIES}) set(BOOST_CLANG_TEST_SOURCES ${SOURCES} main.cpp) add_executable(boost_clang_test ${BOOST_CLANG_TEST_SOURCES}) target_link_libraries(boost_clang_test ${LIBS}) main.cpp: #include <stdio.h> #include <iostream> #include <sstream> #include <string> #include <boost/filesystem.hpp> using namespace std; using namespace boost::filesystem; const char *progname; int main(int argc, char **argv){ return 0; } Thanks in advance.

3 4

[graph] kamada_kawai_spring_layout warnings
by Michael Olea 21 Jun '14

21 Jun '14

Hi. I'm getting compiler warnings for subscripts out of range from kamada_kawai_spring_layout.hpp. I'm using boost_55_0, compiled with clang: Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn) Target: x86_64-apple-darwin13.2.0 Thread model: posix ../../../../../include/boost/graph/kamada_kawai_spring_layout.hpp:110:49: warning: array index 2 is past the end of the array (which contains 2 elements) [-Warray-bounds] double denom = mat[0][0] * (mat[1][1] * mat[2][2] - mat[2][1] * mat[1][2]) The offending code is: template <> struct linear_solver<3> { template <typename Vec> static Vec solve(double mat[2][2], Vec rhs) { double denom = mat[0][0] * (mat[1][1] * mat[2][2] - mat[2][1] * mat[1][2]) - mat[1][0] * (mat[0][1] * mat[2][2] - mat[2][1] * mat[0][2]) + mat[2][0] * (mat[0][1] * mat[1][2] - mat[1][1] * mat[0][2]); double x_num = rhs[0] * (mat[1][1] * mat[2][2] - mat[2][1] * mat[1][2]) - rhs[1] * (mat[0][1] * mat[2][2] - mat[2][1] * mat[0][2]) + rhs[2] * (mat[0][1] * mat[1][2] - mat[1][1] * mat[0][2]); double y_num = mat[0][0] * (rhs[1] * mat[2][2] - rhs[2] * mat[1][2]) - mat[1][0] * (rhs[0] * mat[2][2] - rhs[2] * mat[0][2]) + mat[2][0] * (rhs[0] * mat[1][2] - rhs[1] * mat[0][2]); double z_num = mat[0][0] * (mat[1][1] * rhs[2] - mat[2][1] * rhs[1] ) - mat[1][0] * (mat[0][1] * rhs[2] - mat[2][1] * rhs[0] ) + mat[2][0] * (mat[0][1] * rhs[1] - mat[1][1] * rhs[0] ); Vec result; result[0] = x_num / denom; result[1] = y_num / denom; result[2] = z_num / denom; return result; } }; Looks like it should be: static Vec solve(double mat[3][3], Vec rhs) ... No?

1 0