[1.45] Beta 1 release candidates

[1.45] Beta 1 release candidates are available at http://boost.cowic.de/rc/ As usual, please report success or failure doing builds. We like to get reports of successful builds on several varied platforms before the files are pushed out to SourceForge and the formal announcement made. Thanks, --Beman

On 11/6/2010 12:09 PM, Beman Dawes wrote:
[1.45] Beta 1 release candidates are available at http://boost.cowic.de/rc/
As usual, please report success or failure doing builds. We like to get reports of successful builds on several varied platforms before the files are pushed out to SourceForge and the formal announcement made.
Beman, We're still showing active showstoppers for 1.45 (https://svn.boost.org/trac/boost/report/29). If we ship anyway, we need to have a discussion about what "showstopper" means, and we need a policy for what to do about them prior to release. I suggest that we make a concerted effort to contact the maintainers in question and see what their plans are for addressing these bugs. If the maintainers say they're not showstoppers, we correct the bug's priority. If they can fix them in a reasonable amount of time, we hold the release. If we can't reach them, or if they can't provide a fix in a reasonable time, we bump the Milestone to release+1 and ship with a BIG warning in the release notes about serious outstanding bugs. Also, for future releases, we need to notify maintainers early that they have active showstoppers assigned to them. Perhaps we can even set up automatic daily nag mail as the release approaches. Thoughts? -- Eric Niebler BoostPro Computing http://www.boostpro.com

On 11/6/2010 11:18 AM, Eric Niebler wrote:
On 11/6/2010 12:09 PM, Beman Dawes wrote:
[1.45] Beta 1 release candidates are available at http://boost.cowic.de/rc/
As usual, please report success or failure doing builds. We like to get reports of successful builds on several varied platforms before the files are pushed out to SourceForge and the formal announcement made.
Beman,
We're still showing active showstoppers for 1.45 (https://svn.boost.org/trac/boost/report/29). If we ship anyway, we need to have a discussion about what "showstopper" means, and we need a policy for what to do about them prior to release.
And there's now one less item on that report. Not because it was fixed.. But because I marked one of the build tickets as not a showstopper. Because it's a problem on a non-release compiler/platform. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail

We're still showing active showstoppers for 1.45 (https://svn.boost.org/trac/boost/report/29). If we ship anyway, we need to have a discussion about what "showstopper" means, and we need a policy for what to do about them prior to release.
They may well be addressable, but I note that most have only just been filed - maybe we need a cutoff date past which folks can't file showstoppers for the next release on the grounds that it's probably already too late? John.

John Maddock wrote:
We're still showing active showstoppers for 1.45 (https://svn.boost.org/trac/boost/report/29). If we ship anyway, we need to have a discussion about what "showstopper" means, and we need a policy for what to do about them prior to release.
They may well be addressable, but I note that most have only just been filed - maybe we need a cutoff date past which folks can't file showstoppers for the next release on the grounds that it's probably already too late?
No release or schedule is so important that a release should be pushed when there is an outstanding showstopper issue, period. Doing otherwise means to sacrifice the quality for which Boost has been and should be known. Reclassifying an issue may be appropriate, or an issue may have appeared after a release is pushed, but an empty showstoppers report should be a prerequisite for a release to be announced. Of course, a last minute issue could appear. In that case, assess its severity then reclassify it or query the list for consensus on how to proceed if there is no obvious recourse. Eric's idea to push library owners to clear showstoppers is necessary, too. _____ Rob Stewart robert.stewart@sig.com Software Engineer, Core Software using std::disclaimer; 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.

On Sat, Nov 6, 2010 at 12:18 PM, Eric Niebler <eric@boostpro.com> wrote:
On 11/6/2010 12:09 PM, Beman Dawes wrote:
[1.45] Beta 1 release candidates are available at http://boost.cowic.de/rc/
As usual, please report success or failure doing builds. We like to get reports of successful builds on several varied platforms before the files are pushed out to SourceForge and the formal announcement made.
Beman,
We're still showing active showstoppers for 1.45 (https://svn.boost.org/trac/boost/report/29). If we ship anyway, we need to have a discussion about what "showstopper" means, and we need a policy for what to do about them prior to release.
I'm mainly look for problems that would prevent large swaths of Boost from being used on a given platform. Thus #3550, bootstrap.bat not running on x64 Windows, would appear from the name to be a showstopper. But I tried the bootstrap procedure on my 64-bit Windows 7 system, and it seemed to work as expected. None of the others looked serious enough to hold the beta, although...
I suggest that we make a concerted effort to contact the maintainers in question and see what their plans are for addressing these bugs. If the maintainers say they're not showstoppers, we correct the bug's priority. If they can fix them in a reasonable amount of time, we hold the release. If we can't reach them, or if they can't provide a fix in a reasonable time, we bump the Milestone to release+1 and ship with a BIG warning in the release notes about serious outstanding bugs.
That seems worthwhile and useful, before the actual 1.45.0 release.
Also, for future releases, we need to notify maintainers early that they have active showstoppers assigned to them. Perhaps we can even set up automatic daily nag mail as the release approaches.
That sounds well worth trying. Are you volunteering to set it up for 1.46:-? --Beman

Beman Dawes wrote:
On Sat, Nov 6, 2010 at 12:18 PM, Eric Niebler <eric@boostpro.com> wrote:
On 11/6/2010 12:09 PM, Beman Dawes wrote:
[1.45] Beta 1 release candidates are available at http://boost.cowic.de/rc/
As usual, please report success or failure doing builds. We like to get reports of successful builds on several varied platforms before the files are pushed out to SourceForge and the formal announcement made.
Beman,
We're still showing active showstoppers for 1.45 (https://svn.boost.org/trac/boost/report/29). If we ship anyway, we need to have a discussion about what "showstopper" means, and we need a policy for what to do about them prior to release.
I'm mainly look for problems that would prevent large swaths of Boost from being used on a given platform.
Well, it seems if you think that issue #XXX is not a showstopper, it's best to update issue #XXX so that everybody is on the same page.
Thus #3550, bootstrap.bat not running on x64 Windows, would appear from the name to be a showstopper. But I tried the bootstrap procedure on my 64-bit Windows 7 system, and it seemed to work as expected.
That's because the the primary issue in the ticket was actually fixed long ago and it was left open due to less important follow-ups. I've made adjustments as necessary. - Volodya

On Sun, Nov 7, 2010 at 3:17 AM, Vladimir Prus <vladimir@codesourcery.com> wrote:
Beman Dawes wrote:
...>> I'm mainly look for problems that would prevent large swaths of Boost
from being used on a given platform.
Well, it seems if you think that issue #XXX is not a showstopper, it's best to update issue #XXX so that everybody is on the same page.
Good point, although there is also the question of beta vs final release. There are problems that wouldn't stop a beta but would stop a release.
Thus #3550, bootstrap.bat not running on x64 Windows, would appear from the name to be a showstopper. But I tried the bootstrap procedure on my 64-bit Windows 7 system, and it seemed to work as expected.
That's because the the primary issue in the ticket was actually fixed long ago and it was left open due to less important follow-ups. I've made adjustments as necessary.
Understood. I've done that myself with other tickets. --Beman

Am I correct in thinking that it's still OK to correct documentation glitches in release? Cheers, John.

On 11/7/2010 9:12 AM, John Maddock wrote:
Am I correct in thinking that it's still OK to correct documentation glitches in release?
Yes. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail

Beman Dawes wrote:
[1.45] Beta 1 release candidates are available at [http://boost.cowic.de/rc/
As usual, please report success or failure doing builds. We like to get reports of successful builds on several varied platforms before the files are pushed out to SourceForge and the formal announcement made.
Thanks,
--Beman _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Compiles cleanly (with just a few warnings) on Kubuntu 10.10 64 bit, g++ 4.4.5 . Will test it with my application when the official beta has been released. Best Regards, Ruediger

----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: "Boost Developers List" <boost@lists.boost.org> Sent: Saturday, November 06, 2010 5:09 PM Subject: [boost] [1.45] Beta 1 release candidates
[1.45] Beta 1 release candidates are available at http://boost.cowic.de/rc/
Windows NT msvc-10.Express ====================== Build is OK. Vicente

----- Original Message ----- From: "vicente.botet" <vicente.botet@wanadoo.fr> To: <boost@lists.boost.org> Sent: Wednesday, November 17, 2010 11:00 PM Subject: Re: [boost] [1.45] Beta 1 release candidates
----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: "Boost Developers List" <boost@lists.boost.org> Sent: Saturday, November 06, 2010 5:09 PM Subject: [boost] [1.45] Beta 1 release candidates
[1.45] Beta 1 release candidates are available at http://boost.cowic.de/rc/
mingw gcc 4.50 Build is OK. Vicente

----- Original Message ----- From: "vicente.botet" <vicente.botet@wanadoo.fr> To: <boost@lists.boost.org> Sent: Wednesday, November 17, 2010 11:31 PM Subject: Re: [boost] [1.45] Beta 1 release candidates
mingw gcc 4.50 Build is OK.
There are some errors on Boost.Test when I build gcc-mingw-4.5.0 with c++0x. C:\cygwin\boost\v45>bjam -j2 toolset=gcc --built-type=complete --layout=versioned cxxflags="-std=c++0x" Vicente Building the Boost C++ Libraries. warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. warning: No python installation configured and autoconfiguration note: failed. See http://www.boost.org/libs/python/doc/building.html note: for configuration instructions or pass --without-python to note: suppress this message and silently skip all Boost.Python targets warning: Unable to construct ./stage-unversioned warning: Unable to construct ./stage-unversioned ...patience... ...patience... ...patience... ...found 5849 targets... ...updating 22 targets... gcc.compile.c++ bin.v2\libs\program_options\build\gcc-mingw-4.5.0\debug\link-static\threading-multi\parsers.o libs\program_options\src\parsers.cpp: In function 'boost::program_options::parsed_options boost::program_options::parse_environment(const boost::program_options::options_description&, const boost::function1<std::basic_string<char>, std::basic_string<char> >&)': libs\program_options\src\parsers.cpp:190:36: error: 'environ' was not declared in this scope "g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -g -mthreads -std=c++0x -DBOOST_ALL_NO_LIB=1 -I"." -c -o "bin.v2\libs\program_options\build\gcc-mingw-4.5.0\debug\link-static\threading-multi\parsers.o" "libs\program_options\src\parsers.cpp" ...failed gcc.compile.c++ bin.v2\libs\program_options\build\gcc-mingw-4.5.0\debug\link-static\threading-multi\parsers.o... ...skipped <pbin.v2\libs\program_options\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>libboost_program_options-mgw45-mt-d-1_45.a(clean) for lack of <pbin.v2\libs\program_options\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>parsers.o... ...skipped <pbin.v2\libs\program_options\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>libboost_program_options-mgw45-mt-d-1_45.a for lack of <pbin.v2\libs\program_options\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>parsers.o... ...skipped <pstage\lib>libboost_program_options-mgw45-mt-d-1_45.a for lack of <pbin.v2\libs\program_options\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>libboost_program_options-mgw45-mt-d-1_45.a... gcc.compile.c++ bin.v2\libs\test\build\gcc-mingw-4.5.0\debug\link-static\threading-multi\unit_test_parameters.o In file included from ./boost/test/utils/runtime/cla/dual_name_parameter.hpp:19:0, from ./boost/test/impl/unit_test_parameters.ipp:31, from libs\test\src\unit_test_parameters.cpp:16: ./boost/test/utils/runtime/config.hpp: In function 'void boost::runtime::putenv_impl(boost::runtime::cstring, boost::runtime::cstring)': ./boost/test/utils/runtime/config.hpp:95:51: error: 'putenv' was not declared in this scope "g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -pedantic -g -mthreads -std=c++0x -DBOOST_ALL_NO_LIB=1 -I"." -c -o "bin.v2\libs\test\build\gcc-mingw-4.5.0\debug\link-static\threading-multi\unit_test_parameters.o" "libs\test\src\unit_test_parameters.cpp" ...failed gcc.compile.c++ bin.v2\libs\test\build\gcc-mingw-4.5.0\debug\link-static\threading-multi\unit_test_parameters.o... ...skipped <pbin.v2\libs\test\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>libboost_test_exec_monitor-mgw45-mt-d-1_45.a(clean) for lack of <pbin.v2\libs\test\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>unit_test_parameters.o... ...skipped <pbin.v2\libs\test\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>libboost_test_exec_monitor-mgw45-mt-d-1_45.a for lack of <pbin.v2\libs\test\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>unit_test_parameters.o... ...skipped <pstage\lib>libboost_test_exec_monitor-mgw45-mt-d-1_45.a for lack of <pbin.v2\libs\test\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>libboost_test_exec_monitor-mgw45-mt-d-1_45.a... ...skipped <pbin.v2\libs\test\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>libboost_unit_test_framework-mgw45-mt-d-1_45.a(clean) for lack of <pbin.v2\libs\test\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>unit_test_parameters.o... ...skipped <pbin.v2\libs\test\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>libboost_unit_test_framework-mgw45-mt-d-1_45.a for lack of <pbin.v2\libs\test\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>unit_test_parameters.o... ...skipped <pstage\lib>libboost_unit_test_framework-mgw45-mt-d-1_45.a for lack of <pbin.v2\libs\test\build\gcc-mingw-4.5.0\debug\link-static\threading-multi>libboost_unit_test_framework-mgw45-mt-d-1_45.a... gcc.compile.c++ bin.v2\libs\program_options\build\gcc-mingw-4.5.0\release\link-static\threading-multi\parsers.o libs\program_options\src\parsers.cpp: In function 'boost::program_options::parsed_options boost::program_options::parse_environment(const boost::program_options::options_description&, const boost::function1<std::basic_string<char>, std::basic_string<char> >&)': libs\program_options\src\parsers.cpp:190:36: error: 'environ' was not declared in this scope In file included from ./boost/function/detail/prologue.hpp:17:0, from ./boost/function/function_template.hpp:13, from ./boost/function/detail/maybe_include.hpp:18, from ./boost/function/function1.hpp:11, from ./boost/program_options/value_semantic.hpp:13, from ./boost/program_options/options_description.hpp:13, from ./boost/program_options/detail/cmdline.hpp:14, from ./boost/program_options/parsers.hpp:12, from libs\program_options\src\parsers.cpp:11: ./boost/function/function_base.hpp: In static member function 'static void boost::detail::function::functor_manager_common<Functor>::manage_small(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type) [with Functor = boost::program_options::detail::prefix_name_mapper]': ./boost/function/function_base.hpp:360:11: instantiated from 'static void boost::detail::function::functor_manager<Functor>::manager(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type, mpl_::true_) [with Functor = boost::program_options::detail::prefix_name_mapper, mpl_::true_ = mpl_::bool_<true>]' ./boost/function/function_base.hpp:406:11: instantiated from 'static void boost::detail::function::functor_manager<Functor>::manager(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type, boost::detail::function::function_obj_tag) [with Functor = boost::program_options::detail::prefix_name_mapper]' ./boost/function/function_base.hpp:434:13: instantiated from 'static void boost::detail::function::functor_manager<Functor>::manage(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type) [with Functor = boost::program_options::detail::prefix_name_mapper]' ./boost/function/function_template.hpp:913:60: instantiated from 'void boost::function1<R, T1>::assign_to(Functor) [with Functor = boost::program_options::detail::prefix_name_mapper, R = std::basic_string<char>, T0 = std::basic_string<char>]' ./boost/function/function_template.hpp:722:7: instantiated from 'boost::function1<R, T1>::function1(Functor, typename boost::enable_if_c<boost::type_traits::ice_not<boost::is_integral<Functor>::value>::value, int>::type) [with Functor = boost::program_options::detail::prefix_name_mapper, R = std::basic_string<char>, T0 = std::basic_string<char>, typename boost::enable_if_c<boost::type_traits::ice_not<boost::is_integral<Functor>::value>::value, int>::type = int]' libs\program_options\src\parsers.cpp:233:74: instantiated from here ./boost/function/function_base.hpp:321:15: warning: dereferencing type-punned pointer will break strict-aliasing rules ./boost/function/function_base.hpp:325:13: warning: dereferencing type-punned pointer will break strict-aliasing rules "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -mthreads -std=c++0x -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o "bin.v2\libs\program_options\build\gcc-mingw-4.5.0\release\link-static\threading-multi\parsers.o" "libs\program_options\src\parsers.cpp" ...failed gcc.compile.c++ bin.v2\libs\program_options\build\gcc-mingw-4.5.0\release\link-static\threading-multi\parsers.o... ...skipped <pbin.v2\libs\program_options\build\gcc-mingw-4.5.0\release\link-static\threading-multi>libboost_program_options-mgw45-mt-1_45.a(clean) for lack of <pbin.v2\libs\program_options\build\gcc-mingw-4.5.0\release\link-static\threading-multi>parsers.o... ...skipped <pbin.v2\libs\program_options\build\gcc-mingw-4.5.0\release\link-static\threading-multi>libboost_program_options-mgw45-mt-1_45.a for lack of <pbin.v2\libs\program_options\build\gcc-mingw-4.5.0\release\link-static\threading-multi>parsers.o... ...skipped <pstage\lib>libboost_program_options-mgw45-mt-1_45.a for lack of <pbin.v2\libs\program_options\build\gcc-mingw-4.5.0\release\link-static\threading-multi>libboost_program_options-mgw45-mt-1_45.a... gcc.compile.c++ bin.v2\libs\test\build\gcc-mingw-4.5.0\release\link-static\threading-multi\unit_test_parameters.o In file included from ./boost/test/utils/runtime/cla/dual_name_parameter.hpp:19:0, from ./boost/test/impl/unit_test_parameters.ipp:31, from libs\test\src\unit_test_parameters.cpp:16: ./boost/test/utils/runtime/config.hpp: In function 'void boost::runtime::putenv_impl(boost::runtime::cstring, boost::runtime::cstring)': ./boost/test/utils/runtime/config.hpp:95:51: error: 'putenv' was not declared in this scope "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pedantic -mthreads -std=c++0x -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o "bin.v2\libs\test\build\gcc-mingw-4.5.0\release\link-static\threading-multi\unit_test_parameters.o" "libs\test\src\unit_test_parameters.cpp" ...failed gcc.compile.c++ bin.v2\libs\test\build\gcc-mingw-4.5.0\release\link-static\threading-multi\unit_test_parameters.o... ...skipped <pbin.v2\libs\test\build\gcc-mingw-4.5.0\release\link-static\threading-multi>libboost_test_exec_monitor-mgw45-mt-1_45.a(clean) for lack of <pbin.v2\libs\test\build\gcc-mingw-4.5.0\release\link-static\threading-multi>unit_test_parameters.o... ...skipped <pbin.v2\libs\test\build\gcc-mingw-4.5.0\release\link-static\threading-multi>libboost_test_exec_monitor-mgw45-mt-1_45.a for lack of <pbin.v2\libs\test\build\gcc-mingw-4.5.0\release\link-static\threading-multi>unit_test_parameters.o... ...skipped <pstage\lib>libboost_test_exec_monitor-mgw45-mt-1_45.a for lack of <pbin.v2\libs\test\build\gcc-mingw-4.5.0\release\link-static\threading-multi>libboost_test_exec_monitor-mgw45-mt-1_45.a... ...skipped <pbin.v2\libs\test\build\gcc-mingw-4.5.0\release\link-static\threading-multi>libboost_unit_test_framework-mgw45-mt-1_45.a(clean) for lack of <pbin.v2\libs\test\build\gcc-mingw-4.5.0\release\link-static\threading-multi>unit_test_parameters.o... ...skipped <pbin.v2\libs\test\build\gcc-mingw-4.5.0\release\link-static\threading-multi>libboost_unit_test_framework-mgw45-mt-1_45.a for lack of <pbin.v2\libs\test\build\gcc-mingw-4.5.0\release\link-static\threading-multi>unit_test_parameters.o... ...skipped <pstage\lib>libboost_unit_test_framework-mgw45-mt-1_45.a for lack of <pbin.v2\libs\test\build\gcc-mingw-4.5.0\release\link-static\threading-multi>libboost_unit_test_framework-mgw45-mt-1_45.a... ...failed updating 4 targets... ...skipped 18 targets...

----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: "Boost Developers List" <boost@lists.boost.org> Sent: Saturday, November 06, 2010 5:09 PM Subject: [boost] [1.45] Beta 1 release candidates
[1.45] Beta 1 release candidates are available at http://boost.cowic.de/rc/
With gcc-mingw-4.6.0 c++0x there is a compile error on the Build gcc.compile.c++ bin.v2\libs\regex\build\gcc-mingw-4.6.0\debug\link-static\threading-multi\posix_api.o In file included from ./boost/regex/v4/perl_matcher.hpp:578:0, from ./boost/regex/v4/regex.hpp:88, from ./boost/regex.hpp:31, from libs\regex\build\..\src\posix_api.cpp:22: ./boost/regex/v4/perl_matcher_non_recursive.hpp: In member function 'bool boost::re_detail::perl_matcher<BidiIterator, Allocator, traits>::unwind_short_set_repeat(bool)': ./boost/regex/v4/perl_matcher_non_recursive.hpp:1394:85: error: invalid use of incomplete type 'const struct boost::regex_traits_wrapper<traits>' ./boost/regex/v4/regex_traits.hpp:163:8: error: declaration of 'const struct boost::regex_traits_wrapper<traits>' ./boost/regex/v4/perl_matcher_non_recursive.hpp:1394:85: error: invalid type argument of unary '*' Vicente
participants (8)
-
Beman Dawes
-
Eric Niebler
-
John Maddock
-
Rene Rivera
-
Ruediger Berlich
-
Stewart, Robert
-
vicente.botet
-
Vladimir Prus