- Boost - lists.boost.org

Re: [boost] Boost regression notification (2005-06-28)
by JOAQUIN LOPEZ MU?Z 03 Jul '05

03 Jul '05

----- Mensaje original ----- De: Joel de Guzman <joel(a)boost-consulting.com> Fecha: Martes, Junio 28, 2005 8:16 pm Asunto: Re: [boost] Boost regression notification (2005-06-28) > Douglas Gregor wrote: > > Boost regression test failures > > > > |spirit| > > action_tests: vc-6_5 > > action_tests_debug: vc-6_5 > > ast_calc_tests: vc-6_5 > > ast_calc_tests_debug: vc-6_5 > [...] > > traverse_tests: vc-6_5 > > traverse_tests_debug: vc-6_5 > > while_p_as_parser_tests: vc-6_5 > > while_tests: vc-6_5 > > while_tests_debug: vc-6_5 > > Yaiks! What happened? VC6.5 is supposed to be an unsupported > (unusable) compiler for Spirit 1.8.x. > metacomm has begun using the vc-6_5 toolset, which is an alias of the old msvc toolset. Markup in status/explicit-failures-markup.xml has to be duplicated for this alternative name. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

5 4

Re: [boost] [function_type] Tag types documentation
by Dave Gomboc 03 Jul '05

03 Jul '05

> Tag Types: > ---------- > > The Function Type library uses tag types to represent one > more attributive > properties of a type, such as its variadicness or its calling > convention. "one more"? Did you mean "one or more"? "a type"? It might be one type per tag, but tagging can be applied to more than one type, so this should be rephrased. "variadicness"? I think you meant "variadicity". I'm not thrilled by "attributive properties" either. My discomforture with this phrase is due to its perceived redundancy. Is it common for properties to exist that attribute nothing? I propose: The Function Type library uses tag types to denote properties of types. For example, the tag tag<fastcall, variadic> may be used to denote use of the fast calling convention in combination with variadicity. > When several tags for the same property appear in the > argument list, only the last > one is used; others are ignored. > > tag<nonvariadic,variadic> // same as 'variadic' The semantics of tag<nonvariadic, variadic> should be identical to the semantics of tag<variadic, nonvariadic>. It strikes me as erroneous that this combination of denotations would not yield a compilation error. Have you a well-founded argument for this choice? I'm new to this thread; apologies if I'm rehashing something that was settled earlier. Dave Gomboc

2 2

Re: [boost] [iostreams][vc8]deprecetedstandardlibrarymemberfunctions; fatal linker error
by Peter Foley 03 Jul '05

03 Jul '05

Hi Jonathan, Not sure if you have seen this information: http://lab.msdn.microsoft.com/vs2005/uninstall/ Also try the tool that it talks about on the page. This information helped me uninstall beta 1. Hope this helps. Peter. "Jonathan Turkanis" <technews(a)kangaroologic.com> wrote in message news:<da6fc9$qr4$1(a)sea.gmane.org>... > If only I knew! The first few times I tried to install it, the installer > crashed. I tried again last night, and it fails with a bunch of error messages; > I guess there's still residue in the registry from the failed installations. I > really don't care that much about beta 2; what I'm worried about is the release > version, which I'm afraid won't install either. > > Jonathan

1 0

[function_type] Tag types documentation
by Tobias Schwinger 02 Jul '05

02 Jul '05

Tag Types: ---------- The Function Type library uses tag types to represent one more attributive properties of a type, such as its variadicness or its calling convention. Tags that represent the values of a single property are called property tags. These tags can be used to determine whether one property of a type has a particular value. is_function< T, variadic > is_function< T, default_call > A compound property tag describes a combination of possible values of different properties. The tag class template can be used to create a specific compound property tag. tag<default_call,variadic> When several tags for the same property appear in the argument list, only the last one is used; others are ignored. tag<nonvariadic,variadic> // same as 'variadic' The following code creates the type int __fastcall (int...). function_type<mpl::vector<int,int>, tag<variadic,fastcall> >::type All properties not described by the tag acquire a default. The next example creates the type of a (variadic) function of the default calling convention int(int...). function_type<mpl::vector<int,int>, variadic >::type A compound property tag matches a type only when all of its component properties match: is_function< void __fastcall (...),tag<variadic,fastcall> >::value // is true is_function< void __stdcall (...),tag<variadic,fastcall> >::value // is false [ version with markup: http://tinyurl.com/bxvke ]

1 0

[function_type] Synopsis
by Tobias Schwinger 02 Jul '05

02 Jul '05

Synopsis: --------- namespace boost { namespace function_type { // Classification (header: boost/function_type/classification.hpp) // Result: bool, Concept: MPL-Integral Constant template<typename T, typename Tag = no_attributes> struct is_function; % % struct is_function_pointer; % % struct is_function_reference; % % struct is_member_function_pointer; % % struct is_callable_builtin; // any of the above % % struct is_callable_scalar; // any except undecorated % % struct is_nonmember_callable_builtin; // any except member pointers % % struct is_nonmember_callable_scalar; // function pointer or reference // Synthesis (header: boost/function_type/synthesis.hpp) // Result: type, Concept: Metafunction template<typename T_or_Signature_or_Seq ,typename Tag = no_attributes, typename ClassT = add_reference<_> > struct function_type; % % struct function_pointer; % % struct function_reference; % % struct member_function_pointer; // Decomposition (header: boost/function_type/decomposition.hpp) // Result: bool, Concept: MPL-Integral Constant template<typename T> struct arity<T>; // Result: type, Concept: Metafunction template<typename T> struct class_of; template<typename T> struct result; template<typename T, typename Index> struct parameter; template<typename T, std::size_t Index> struct parameter_c; template<typename T, typename Index> struct effective_parameter; template<typename T, std::size_t Index> struct effective_parameter_c; // Concept: MPL Random-Access Sequence template<typename T> struct parameters; template<typename T, typename ClassT = add_reference<_> > struct effective_parameters; // Concept: MPL Extensible/Random-Access Sequence and Tag template<typename T, typename ClassT = add_reference<_> > struct signature; // Tags (no header needed - "just there") template<typename Tag1, typename Tag2 = ... struct tag; // - variadic property // defaults to 'nonvariadic' with synthesis typedef /.../ nonvariadic; typedef /.../ variadic; // - const aspect (ignored for nonmember functions) // defaults to the const qualification of the class type with synthesis typedef /.../ const_member; typedef /.../ nonconst_member; // - volatile aspect (ignored for nonmember functions) // defaults to the volatile qualification of the class type with synthesis typedef /.../ volatile_member; typedef /.../ nonvolatile_member; // Calling convention aspect // defaults to default_call when used with synthesis typedef /.../ default_call; typedef /.../ cdecl, stdcall, etc. (depends on configuration) } }

1 0

[function_type] attempt to freeze interface and tags documentation
by Tobias Schwinger 02 Jul '05

02 Jul '05

Just reply hook for me to bundle other posts.

1 0

Formal Review: Typeof
by Andy Little 02 Jul '05

02 Jul '05

The formal review of Arkadiy Vertleyb and Peder Holt's Typeof library begins today, May 20th 2005. The review period will continue until the 30th of May. The proposed Typeof library emulates the functionality of the non-standard 'typeof' operator, and incomplete implementations of decltype and the proposed 'auto' declarator , described in http://www.osl.iu.edu/~jajarvi/publications/papers/decltype_n1478.pdf. It is commonly acknowledged that this type of functionality is sorely needed and should be standardardised in the language. For compliant compilers the library requires some help in the form of registration macros but, because use of typeof is by its nature most likely in generic libraries, it is expected that this can often be done by the library author rather than the user. In some cases the compilers capabilities (by means of extensions and even compiler bugs) have been used to remove the need for registration. However, for portability and in order to test emulation mode on the compilers where it is available but not used by default (VC7.1, GCC etc), #define BOOST_TYPEOF_COMPLIANT [see note *1*]. Testing the emulation is useful, even on compilers that provide a better option, to get a rounded view of the library and its capabilities. I hope you will find time to write a review of the library, which is available at: http://boost-sandbox.sourceforge.net/vault/ , typeof.zip The system has been tested with the following compilers: MSVC 6.5/7.0/7.1/8.0; [see note *1* regarding VC7.0 and VC6.5] GCC 3.4.2 (The following is a quote from : http://www.boost.org/more/formal_review_process.htm ) Here are some questions you might want to answer in your review: What is your evaluation of the design? What is your evaluation of the implementation? What is your evaluation of the documentation? What is your evaluation of the potential usefulness of the library? Did you try to use the library? With what compiler? Did you have any problems? How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? Are you knowledgeable about the problem domain? And finally, every review should answer this question: Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Andy Little Typeof review manager notes: *1* MSVC6.5 and VC7.0 are not supported by the BOOST_TYPEOF_COMPLIANT macro

9 43

Re: [boost] Regressions in your Boost libraries as of 2005-06-30
by David Abrahams 02 Jul '05

02 Jul '05

Douglas Gregor <dgregor(a)cs.indiana.edu> writes: > You are receiving this report because one or more of the libraries you > maintain has regression test failures that are not accounted for. > A full version of the report is sent to the Boost developer's mailing > list. What's going on here? Is intel-win32-8_1 a new platform? A couple of days ago I only had a few gcc-3.3.6-linux regressions to deal with. > There are failures in these libraries you maintain: > iterator (2) > python (56) > > |iterator| > filter_iterator_test: intel-win32-8_1 > lvalue_concept_fail: intel-win32-8_1 > > |python| > andreas_beyer: intel-win32-8_1 > args: intel-win32-8_1 <snip> -- Dave Abrahams Boost Consulting www.boost-consulting.com

3 2

[logging] flushing logs
by Greg Landrum 02 Jul '05

02 Jul '05

I'm just getting started with John Torjo's logging library. So far the library looks really useful, but I'm having problems understanding the timing/sequencing of output by the logging objects. I'm trying to get the logs to dump their output to std:cerr immediately: // ----------------------------- #include <iostream> #include <boost/log/log.hpp> #include <boost/log/functions.hpp> namespace logging = boost::logging; BOOST_DECLARE_LOG(cerrLog); BOOST_DEFINE_LOG(cerrLog,"cerrLog"); void write_to_cerr(const std::string &, const std::string &msg) { std::cerr << msg; std::cerr.flush();} int main(){ logging::add_modifier("cerrLog",logging::prepend_time("[$hh:$mm:$ss] "), logging::DEFAULT_INDEX-10); logging::add_appender("cerrLog",write_to_cerr,logging::DEFAULT_INDEX+1); std::cerr << "1" << std::endl; BOOST_LOG(cerrLog) << "2" << std::endl; std::cerr << "3" << std::endl; BOOST_LOG(cerrLog) << "4" << std::endl; } // ----------------------------- However, the output from running this is always something like: 1 3 [14:56:35] 2 [14:56:35] 4 So the logger output is "late". Is there some flag I can set (or appender I can use) that will force output to go to the target streams immediately or is this outside the design of the logging library? In the event that it matters: I'm using version 1.33 of the logging library and I've tested this on both Windows (vs .net 2003) and Linux (g++ v3.2). Thanks, -greg

3 3

[Boost-bugs] [ boost-Bugs-1231573 ] sorry, unimplemented: call_expr cannot be mangled
by SourceForge.net 02 Jul '05

02 Jul '05

Bugs item #1231573, was opened at 2005-07-02 20:20 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1231573&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: type_traits Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mattias Ellert (mattiasellert) Assigned to: John Maddock (johnmaddock) Summary: sorry, unimplemented: call_expr cannot be mangled Initial Comment: [ellert@ellert boost-test]$ rpm -q boost boost-1.32.0-5.fc3 [ellert@ellert boost-test]$ gccxml --version GCC-XML version 0.7.0 [ellert@ellert boost-test]$ gccxml -fxml=test.xml -I. test.h /usr/include/boost/tuple/detail/tuple_basic.hpp:311: sorry, unimplemented: call_expr cannot be mangled due to a defect in the C++ ABI If I apply the attached patch to boost/type_traits/config.hpp it works: [ellert@ellert boost-test]$ gccxml -fxml=test.xml -I. -Ipatched test.h [ellert@ellert boost-test]$ (I have removed the "xml_find_template_parm encountered unsupported type" messages in the output above for clarity.) The files used in the example are attached in the tarfile. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1231573&group_… ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0