- Boost - lists.boost.org

Vector quantity?
by sultana rashid 15 Feb '12

15 Feb '12

Hello all, I was finding something on Vector quantity in Boost library, as: Vector decomposition ,cross product,absolute value of a vector quantity ,projection of a vector etc. I am afraid whether I could not find or Boost missing it. Thanking you, Sultana rashid.

2 1

FW: Snobol4 matching in C++
by Steven Kibler 15 Feb '12

15 Feb '12

I have an implementation of Snobol4 patterns and pattern matching that runs in C++. All of the Snobol4 patterns and replacements are implemented in addition to numerous extensions that have proven useful over the years. The patterns are built with overloaded operators and building patterns is simple, straight forward, easy to read and test. In many cases, I find that Snobol4 patterns and its matching algorithm is clearer, more intuitive, and more useful than regular expressions. I have been able to typically cut the required lines of code to accomplish pattern matching by half or a third over using regular expressions. The package is well integrated into C++ and its data types. For post circa 1980 'newbies' unaware of the power of Snobol4, a description of Snobol4 can be seen in a copy of several Snobol4 manuals at ftp://ftp.snobol4.com/spitman.pdf and ftp://ftp.cs.arizona.edu/snobol/gb.pdf. I would like the package to be published under the auspices of Boost. I would like to know if this package would be something that the users of the Boost community would be interested in. This package was originally written in Ada by Robert Dewar and AdaCore, translated to C/C++ by Philip Budne, and cleaned up and expanded by me. The Philip Budne version may be found at http://www.snobol4.org/ (Look for the SPIPAT link) along with many other references for SNOBOL and SPITBOL. Thanks Steven Kibler Facet Soft Tech, Inc.

1 0

[local_function] trunk commit
by lcaminiti 15 Feb '12

15 Feb '12

Hello all, I have committed Boost.LocalFunction (and related libraries) to trunk. This is my first commit to Boost trunk :) . I will monitor this ML closely and I will be ready to make any fix in real-time in case I have broken something. However, I have ran all regressions tests of what I committed using MSVC 8.0 and GCC 4.5.3 (with and without C++0x features) and they all pass. I also have ran Boost's inspect on all files I committed. Boost.LocalFunction (new) boost/local_function[.hpp] libs/local_function Boost.ScopeExit (improved) boost/scope_exit.hpp libs/scope_exit Boost.Functional/OverloadedFunction (new) boost/functional/overloaded_function[.hpp] libs/functional/overloaded_function Boost.Utility/IdentityType (new) boost/utility/identity_type.hpp libs/utility/identity_type Thanks for your support and understanding. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-local-function-trunk-commit-tp4389… Sent from the Boost - Dev mailing list archive at Nabble.com.

1 0

Re: [boost] [filesystem] operations.hpp Won't Compile with VC10 using Boost 1.47
by Stewart, Robert 14 Feb '12

14 Feb '12

Stephan T. Lavavej wrote: > [Robert Stewart] > > When I try to include boost/filesystem/operations.hpp, my > > code won't compile on MSVC 10 (Visual Studio 2010). > > The error is from boost/filesystem/v3/config.hpp:49: > > # if defined( BOOST_NO_STD_WSTRING ) > > # error Configuration not supported: Boost.Filesystem V3 > and later requires std::wstring support > > # endif > > First, check your command line. If it isn't defining the > macro, preprocess with /P /d1PP . The second option is > undocumented and unsupported, but extremely useful - it > preserves #define directives, so you can see where macros are > coming from. I was looking for such an option! BOOST_NO_STD_WSTRING didn't appear in the output. This was a false alarm. Why does VC print #error messages that are conditionally compiled and don't apply! In this case, BOOST_NO_STD_WSTRING is *not* defined, yet the #error still appears in the output: In file included from D:/.../Boost/boost_1_47/include/boost-1_47/boost/filesystem/operations.hpp:31, from controller.cpp:22: D:/.../Boost/boost_1_47/include/boost-1_47/boost/filesystem/v3/operations.hpp:21:5: #error Configuration not supported: Boost.Filesystem V3 and later requires std::wstring support Emacs' compilation-mode dutifully marks that as an error and I didn't realize that the build progressed past that point. Arrrggghhh! Thanks for your help. _____ Rob Stewart robert.stewart(a)sig.com Software Engineer using std::disclaimer; Dev Tools & Components Susquehanna International Group, LLP http://www.sig.com ________________________________ IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.

2 2

[bjam] command for release/debug
by lcaminiti 14 Feb '12

14 Feb '12

Hello all, How can I program a Jamfile to execute the following on `bjam debug`: compile-fail const_block_err.cpp ; But the following on `bjam release`? run const_block_err.cpp ; Thanks. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-bjam-command-for-release-debug-tp4… Sent from the Boost - Dev mailing list archive at Nabble.com.

2 1

[filesystem] operations.hpp Won't Compile with VC10 using Boost 1.47
by Stewart, Robert 14 Feb '12

14 Feb '12

When I try to include boost/filesystem/operations.hpp, my code won't compile on MSVC 10 (Visual Studio 2010). The error is from boost/filesystem/v3/config.hpp:49: # if defined( BOOST_NO_STD_WSTRING ) # error Configuration not supported: Boost.Filesystem V3 and later requires std::wstring support # endif I found only the following places where BOOST_NO_STD_WSTRING is defined, and none should apply, so I'm at a loss to understand why my build fails. What have I missed? ./config/platform/amigaos.hpp:12:#define BOOST_NO_STD_WSTRING ./config/platform/symbian.hpp:85:# define BOOST_NO_STD_WSTRING ./config/stdlib/libstdcpp3.hpp:23:# define BOOST_NO_STD_WSTRING ./config/stdlib/modena.hpp:22:#define BOOST_NO_STD_WSTRING ./config/stdlib/sgi.hpp:100:# define BOOST_NO_STD_WSTRING ./config/stdlib/stlport.hpp:109:# define BOOST_NO_STD_WSTRING _____ Rob Stewart robert.stewart(a)sig.com Software Engineer using std::disclaimer; Dev Tools & Components Susquehanna International Group, LLP http://www.sig.com ________________________________ IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.

2 1

[config] Flags for default/delete special member functions?
by Daryle Walker 14 Feb '12

14 Feb '12

Can we add macro constants to boost/config.hpp that indicate if marking (special) member functions as "= default" or "= delete" is supported? Daryle W.

2 1

[trunk] compilation errors on MSVC 8
by lcaminiti 14 Feb '12

14 Feb '12

Hello all, I get the errors below if I run bootstrap from the latest trunk checkout using MSVC 8 on Windows 7... (the trunk seems instead to work with GCC 4.5.3 on Cygwin). Thanks. --Lorenzo Setting environment for using Microsoft Visual Studio 2005 x86 tools. ### ### Using 'vc8' toolset. ### C:\Users\lorcam\Desktop\code\boost-trunk\tools\build\v2\engine>if exist bootstrap rd /S /Q bootstrap C:\Users\lorcam\Desktop\code\boost-trunk\tools\build\v2\engine>md bootstrap C:\Users\lorcam\Desktop\code\boost-trunk\tools\build\v2\engine>cl /nologo /RTC1 /Zi /MTd /Fobootstrap/ /Fdbootstrap/ -DNT -DYYDEBUG -wd4996 kernel32.lib advapi32.lib user32.lib /Febootstrap\jam0 command.c compile.c constants.c debug.c execnt.c filent.c function.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c object.c option.c output.c parse.c pathunix.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c md5.c pwd.c class.c w32_getreg.c native.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c command.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' compile.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' constants.c debug.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' execnt.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' filent.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' function.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' glob.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' hash.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' hdrmacro.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' headers.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' jam.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' jambase.c jamgram.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' lists.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' make.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' make1.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' object.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' option.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' output.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' Generating Code... Compiling... parse.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' pathunix.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' regexp.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' rules.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' scan.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' search.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' subst.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' timestamp.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' variable.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' modules.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' strings.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' filesys.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' builtins.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' md5.c pwd.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' class.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' w32_getreg.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' native.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' set.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' path.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' Generating Code... Compiling... regex.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' property-set.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' sequence.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' order.c c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2016: C requires that a struct or union has at least one member c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(466) : error C2061: syntax error : identifier 'pid_t' c:\users\lorcam\desktop\code\boost-trunk\tools\build\v2\engine\jam.h(468) : error C2059: syntax error : '}' Generating Code... -- View this message in context: http://boost.2283326.n4.nabble.com/boost-trunk-compilation-errors-on-MSVC-8… Sent from the Boost - Dev mailing list archive at Nabble.com.

3 3

Re: [boost] [optional] generates unnessesary code for trivial types
by Andrzej Krzemienski 14 Feb '12

14 Feb '12

> > But even that appears like a non-obvious thing to me. Would other people > > here in the list, and also developers in general agree that it is ok that > > you have output operation but no input operation? I think that in the > > standard library they always go in pairs. (I am not sure, though). > > In my own code I often find myself defining only output operators. For things > more complex than enums or numerics I usually handle input with specialized > solutions, with tools line Boost.Spirit. As for the standard library, I'm not > sure but dos thread::id have an input operator? > > Also, how would you implement it? what should an uninitialized optional > > print? Nothing? but how is having printed an uninitialized optional<int> > > different that not having printed anything? A question mark? but how would > > the following two be different: > > FWIW, boost::optional provides both input and output. > > If you propose to provide only output operation, then it looks like you > > want this for some sort of logging. But perhaps it is better to have some > > overloaded function toString() that converts all the types to strings. > > Usually the string format that works for one program does not work for the > > other. And there appears to be no natural/intuitive way of representing any > > type (like optional) as text. > > I usually dislike toString and alike methods. I think, manipulators are more > flexible and modularized approach. Do you think it would be possible to > provide different manipulators to fulfill different IO requirements? I have checked the standard and indeed thread::id provides operator<< without the matching operator>>, so this asymmetry would not be a precedent in the standard. Although the situation with thread::id is speciffic. ID's are assigned by the OS and trying to assign them by other means would definitely be an error. I also checked boost::optional and it provides both (I learned two new things today). Uninitialized optional of any type renders "--" (two dashes); whereas initialize optional always prepends a space. I am not sure if this does not look like hack; but people already said this would not be much of a problem. Certainly, there ways to make the output of optional configurable. I am not sure manipulators would be my preference. An alternative would be the approach that Boost.Date_time has adopted: you set your preference per stream (plus one global setting) by means of locale mechanism. However, when it comes to proposing stuff in front of the ISO committee, there is one other factor, which I failed to mention yet. It is the "fragility" of the process. I am concerned that if anything turns out to be controversial, the whole Optional would be at risk of being rejected. This might be an exaggeration (I have never gone through the process of proposing something and then pushing it through), but Optional has already been proposed by Fernando (http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1878.htm) and rejected; primarily for two things: operators -> and * and the semantics for optional reference assignment (see http://lists.boost.org/Archives/boost/2005/10/95079.php) I would much like to avoid the situation where Optional (which I believe is very useful to wide variety of programmers) would be rejected because of one additional, however tiny, controversy of streaming operator. Regards, &rzej

3 2

Re: [boost] [optional] generates unnessesary code for trivial types
by Hite, Christopher 14 Feb '12

14 Feb '12

From: Domagoj Saric <domagoj.saric(a)littleendian.com> > > Maybe I'm missing something, but I don't see the justification. > IMO it seems that, yes, you are making the same mistake as Lucanus, thinking > about "The Universe" only as/through your POV of your personal problem domain: > a) (optional models optionally holding an object) + (objects can be held by > value and by reference) = optional<T&> perfectly logical I'm really not. Give me a use case. Do they make sense being passed as parameters/returns? Do they make sense being stored? I just see some corner case of optional being turned into a replacement for regular pointer. Why not just make dumb_ptr<T>? If you want you can make it streamable and give it clean construction. What is it you really want from optional<T&>? Does anyone use it a lot? Is it like std::vector<bool>? > b) creating special cases (e.g. for T&) creates special problems in generic code My point exactly. I'd make it work for completeness but not bother to optimize. Chris

4 6