September 2004 - Boost - lists.boost.org

OutFrmt lib design questions
by Rozental, Gennadiy 20 Sep '04

20 Sep '04

Hi, Here some question I've got while reading submitted library. 1. What is an advantage if using this library for scalar types (vs. defining operator<<) 2. If primary target is collection formatting wouldn't it be better to name library "collection formats something"? 3. If there is a way to assign format to collection/type combination permanently (through global operator <<), why would I want to do it in every instance of output operation? 4. What is an advantage of using this library to assign format to collection/type combination permanently vs. explicit implementation (using FOREACH construct for example) 5. Why do we need boost::io::range? Couldn't we use boost::range instead? 6. In a formatter usage how would I guess what is what? boost::io::formatter< char * > fmt( "\ ", " /", " | " ); boost::io::formatob( vec, boost::io::containerfmt()).format( fmt ); 7. Who come format calls order dependent? boost::io::formatob( vec, boost::io::containerfmt()).format( fmt ).format( " : " ); 8. If I got vector<vector<int> >. How do I supply separators for both internal and external vectors? 9. Let say I print vector<char>. Is there way to print it like this: { 'a', 'b', '0x01', ' ' } That's enough for now. Please comment. Gennadiy.

1 0

[boost.range] late addition, votes needed
by Thorsten Ottosen 20 Sep '04

20 Sep '04

Dear All, In the pre-redmond mailing Walter Brown discusses the possibility of adding these members to standard container classes: const_iterator cbegin(); const_iterator cend(); const_reverse_iterator crbegin(); const_reverse_iterator crbegin(); The motiviation is that we want to be able to say explicitly "give me a const iterator" without doing ugly casts. IMO a sound idea. Given the framework in boost.range these would be absolutely *trivial* to add. 1st vote: for or against adding these? 2nd vote: which naming scheme to use: a: cbegin(), cr_begin() b: const_begin(); const_rbegin(); The motivation for chosing the latter could be that "cr" contracttions become harder to read. Let me know what ya think. best regards Thorsten

14 39

Re:[boost] Re: python/detail/config.hpp bug?
by Robert Ramey 20 Sep '04

20 Sep '04

"Aleksey Gurtovoy" <agurtovoy(a)meta-comm.com> writes: >> Boost.Python fails to build with MSVC 6.x/STLPort (see >> http://tinyurl.com/4nl7l) due to the following (incorrect) >> configuration logic in >> "boost/python/detail/config.hpp": >> >> // The STLport puts all of the standard 'C' library names in std (as >> far as the // user is concerned), but without it you need a fix if >> you're using MSVC or // Intel C++ # if >> defined(BOOST_MSVC_STD_ITERATOR) # define BOOST_CSTD_ # else # >> define BOOST_CSTD_ std # endif >> >> The issue, as explained in "boost/config/stdlib/stlport.hpp" is that: >> >> // STLport does a good job of importing names into namespace std::, // >> but doesn't always get them all, define BOOST_NO_STDC_NAMESPACE, since >> our // workaround does not conflict with STLports: >> >> Is there a reason why we are not using BOOST_NO_STDC_NAMESPACE here? I had similar problems in my setup. I fixed them by close looking at the release notes for stlport 4.5.3 and found that stlport 4.5.3 puts an altered copy of stlport directory into the msvc include directory. I set environmental variables export STLPORT_PATH="c:/" export STLPORT_VERSION=4.5.3 export STLPORT_INCLUDE_DIRECTORY="c:/program files/Microsoft Visual Studio/vc98/include/stlport" This permitted compile link and test with msvc-stlport toolset. I believe it would also help intel-7.1-v6-stlport-4.5.3 toolset builds. Robert Ramey

1 0

RE: [boost] Re: Re:Re: [static_assert] Regression with gcc 3.4.2?
by Ben Hutchings 20 Sep '04

20 Sep '04

Jonathan Turkanis <technews(a)kangaroologic.com> wrote: > "Robert Ramey" <ramey(a)rrsd.com> wrote in message > news:20040919040443.D18A931132@acme.west.net... > > "David B. Held" <dheld(a)codelogicconsulting.com> wrote in message > > news:cihmvu$3ik$1@sea.gmane.org... > > > #include <boost/static_assert.hpp> > > > > > > template <typename T> > > > struct foo > > > { > > > void bar(void) > > > { > > > BOOST_STATIC_ASSERT(false); > > > } > > > }; > > > > I use > > > > .... > > BOOST_STATIC_ASSERT(sizeof(T) == 0); > > The expression 'always_false<T>::value' can't be evaluated until > the point of instantiation, since always_false could be > specialized for T. OTOH, the compiler can tell immediately that > 'sizeof(T) == 0' is false, so might it not replace > 'sizeof(T) == 0' with 'false', and then issue the same error as > in the quoted case? sizeof(T) isn't always false, because for some types T it isn't even well-formed. As a value-dependent expression I think it must not be evaluated until the template is instantiated.

2 1

RE: [boost] Re: [Output Formatter]: Cascading Style Sheets (CSS)proposal
by Reece Dunn 20 Sep '04

20 Sep '04

Vladimir Prus wrote: Hi Volodya, > >>Do you provide the ability to use different separators for sequences, >sets > >>and maps? > > > > In the review version of the library, there are two sets of default > > values: one for n-ary types formatting as "( a, b )" and one for the >other > > sequence types, formatting as "[ a, b, c ]". In the version I am > > rewriting, I only have one set of default formatting: "[ a, b, c ]". > >That's bad, I'd rather prefer different formatting styles for sets and >vectors. Hmm. Note that this is for the default values, i.e. you can set the formatting you want when constructing a format object construct. > >>Then I don't understand why you can > >>set different default style for those kinds of object, and cannot > >>selectively > >>override the style > > > > Because the way I am storing it on the stream is based on decoration >type > > (open; close; separator) and not on the format object type. > >Why? Is there any specific difficulty with using format object type (or >"kind") as key? The current implementation in the post-review version that I am developing uses a simplified approach in dealing with pword -- it assumes that the type is const CharT * and is not allocated (i.e. is a string literal). It would be possible to do based on format object type, but that would increase the complexity of the code. > > A wrapper_decorator is one that only has open and close decoration >values. > > Thus, it wraps the object associated with it (via a format object): > > > > template< class OutStream, typename T > > > OutStream & write( OutStream & os, const T & elem ) > > { > > return( os << open << elem << close ); > > } > >Is this a method of 'wrapper_decorators'? It is a method of the format object used when writing to a stream. > >>I agree that you might want to store and then restore STL container from >a > >>file, and the library addresses this need to. But I don't understand why > >>you would want to customize the formatting style. Basically, you either > >>should > >>the data to user, or not. In first case, you need a single usable style. > >>For > >>the second case, you might need another "compact" style. I don't see the > >>point of customization. > > > > It is currently possible to state what style formatting an object takes > > using the decorate function (format in the review implementation). Thus: > > > > // review implementation: > > std::cout << io::formatob( vec ).format( "( ", " )" ); // ( a, b, c, >d > > ) > > > > Here, the separator is not set and thus takes the default value (the one > > provided by one of the mechanisms outlined above). > >Ok, aside from naming, the above is fine. The naming issue has been discussed earlier in the review. In the post-review version, the above example is: std::cout << io::object( vec ).decorate( "( ", " )" ); // ( a, b, c, d ) (I know the review is still in process, but I have been working to address the issues in the review version of my library.) > > You might want to customize formatting for various reasons. One example >is > > if you have: > > std::list< std::string > names; > > and want to write that out as a HTML ordered list. You can do the > > following: > > > > std::cout << io::formatob( names ).format( "<ol><li>", "</li></ol>", > > "</li><li>" ); > >Is this a practical use case? Reviewers have requested the ability to generate XML/HTML. This is to show that it is possible to do that within the existing framework. >Well, you can print 'names' this way, but if >you want to print 'Person', you'll need much more powerfull tools. Anyway, >if the overhead is small, no problem. If Person supports << on a stream, you can do: std::list< Person > people; std::cout << io::formatob( people ).format( "<ol><li>", "</li></ol>", "</li><li>" ); > > It is also > > possible to provide a basic form of message localization, reading a > > std::map< std::string, std::string > in from a file. E.g.: > > [snip] >That's more like an artificial example, I think. For practical uses, the >message catalog would have to contain comments, at least, and that again >requires much more complex parser. This is true. Although, you could write a custom state object to skip comments and then bind that to the formatter. >I'll try to write a complete review soon, >so stay tuned ;-) :) (What frequency are you broadcasting at ;)) Regards, Reece _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger

1 0

RE: [boost] [thread] Build failures for CW, found the xtime problem...
by Ben Hutchings 20 Sep '04

20 Sep '04

Rene Rivera <grafik.list(a)redshift-software.com> wrote: > After some investigation I found the problem with the build failures > for xtime.cpp on CW platforms: http://tinyurl.com/5nwxo [1] > > The issue is the placement of the definition of > __STDC_CONSTANT_MACROS to bring in the *INT*_C() constant macros > from cstdint. <snip> > Moving the definition above the <boost/thread/xtime.hpp> included > fixes that problem: <snip> > OK to commit?? <snip> The fix deserves at least a comment. I would move the inclusion of cstdint.hpp along with the macro definition as well.

1 0

RE: [boost] Thread/intel-8.0-linux regressions
by Ben Hutchings 20 Sep '04

20 Sep '04

John Maddock <john(a)johnmaddock.co.uk> wrote: > > Linker output []: > > Chmod1 > > > > ../bin/boost/libs/thread/test/test_tss.test/intel-8.0-linux/debug/ > > threading-multi/test_tss > > > > > > Run output []: > > > > EXIT STATUS: 139 > > > > ? > > > > All thread tests are failing in the similar manner. This is really > > unpleasant given that the library worked on Intel 8.0/Linux in 1.31. > > There are two issues here: > > 1) Intel 8.1 currently crashes on all tests that use the unit test > suite, Intel tell me this will be fixed soon. > 2) Intel 8.0 and 8.1: Martin Wille's tests are run on a Linux version > that unsupported by Intel, as a result all tests that use > <threading>multi fail during program startup, see for example > http://tinyurl.com/4kvja. I don't see a solution to this unless we > can either get someone else to run Intel on Linux, or else persuade > Martin to use a different Linux vendor :-( Are they assuming that later 2.4 kernels have NPTL when that's really only true of certain vendors' patched kernels? If that's the problem then it might be possible to work around it by pointing LD_PRELOAD at a library that makes uname() return an earlier version. That's possibly something of a drastic solution though!

1 0

RE: [boost] Thread/intel-8.0-linux regressions
by Ben Hutchings 20 Sep '04

20 Sep '04

Aleksey Gurtovoy <agurtovoy(a)meta-comm.com> wrote: > Does anybody have any ideas what's up with this > (http://tinyurl.com/6vecl) > > Linker output []: > Chmod1 > ../bin/boost/libs/thread/test/test_tss.test/intel-8.0-linux/debug/ > threading-multi/test_tss > > > Run output []: > > EXIT STATUS: 139 > > ? > > All thread tests are failing in the similar manner. This is really > unpleasant given that the library worked on Intel 8.0/Linux in 1.31. Bits 0-6 are set to 11, indicating termination due to segment violation. Bit 7 is set to 1, indicating that a core dump was saved. Bits 8-15 (normally the exit code) are set to 0 since the program didn't exit.

1 0

RE: [boost] Re: immutable string
by Ben Hutchings 20 Sep '04

20 Sep '04

David B. Held <dheld(a)codelogicconsulting.com> wrote: > Maxim Yegorushkin wrote: > > > I've been working on a small library - an immutable C++ string. Now > > it is in usable state and has been put in use in a couple of real > > projects. Although it needs further polishing, I would like to know > > is there any interest in such a library? > > > > Here is the link: http://conststring.sourceforge.net/ > > First, I'll say that yes, I am very interested in a library such as > this. Second, let me say that "const_string<>" and "immutable string" > don't seem like the right terms to me. The fact that you can call > operator?=() and append() on it tell me that there is little that is > "const" or "immutable" about it. It seems to me that "cow_string<>" > would be more appropriate, but perhaps others have different opinions. I once wrote a string template class similar to this, though without the clever storage policy. Unfortunately this was done in the course of my employment and I left that job without having got permission to make it public. Anyway, I think the name I settled on was atomic_string. > I suppose its not completely a COW string, since you don't support the > full set of mutating operations. <snip> It never modifies buffers once they've been initialised, so it has no use for COW. Ben.

1 0

Re: [boost] [Output Formatter]: Cascading Style Sheets (CSS) proposal
by Reece Dunn 20 Sep '04

20 Sep '04

Vladimir Prus wrote: >Hi Reece, > > > io::sequence_decorators< char > seq( "; " ); > > std::cout << '"' << seq.open( std::cout ) << "\"\n" // "[ " > > << '"' << seq.close( std::cout ) << "\"\n" // " ]" > > << '"' << seq.separator( std::cout ) << "\"\n"; // "; " > > > > where separator( std::cout ) uses the separator value specified by seq >and > > the others use the values set on the std::cout stream. > >I don't understand this phrase, could you clarify. What does it mean to >"use >the separator". "use the separator value": the io::sequence_decorators< char > (io::formatter in the review implementation of the library) type holds 3 io::decoration< char > properties -- open; close; and separator. These are used when performing input/output using my library to render a given type. In the example above, the seq object provides a custom value for the separator decoration. The io::decoration< char >::operator()( StreamType & ) method will look up the default value of the decoration using the stream passed to it unless a custom value is provided. Thus, when accessing the separator value using this method, the custom one is chosen instead of the default one. > > To change these > > defaults, you can use: > > > > std::cout << io::cdecorate( "[{ ", " }]" ); // [{ a, b, c }] > > > > The problem with this is that it changes the defaults for all the > > formatting used, thus you cannot have different defaults for sequences >and > > n-ary types. > >I don't undestand this, either. Probably I've missed something in earlier >messages. What's "n-ary" type? An n-ary type is a type that has a fixed number of elements. std::pair is a 2-ary type, boost::math::quaternion is a 4-ary type, and so on. >Do you provide the ability to use different separators for sequences, sets >and maps? In the review version of the library, there are two sets of default values: one for n-ary types formatting as "( a, b )" and one for the other sequence types, formatting as "[ a, b, c ]". In the version I am rewriting, I only have one set of default formatting: "[ a, b, c ]". >Then I don't understand why you can >set different default style for those kinds of object, and cannot >selectively >override the style Because the way I am storing it on the stream is based on decoration type (open; close; separator) and not on the format object type. > > == Dynamic Styles > > > > You can also set CSS properties within script code, e.g. > > tag.style.fontFamily = "Times New Roman"; > > > > This style behaviour is available in the new decorators, for example: > > io::wrapper_decorators< char > wrap; > > wrap.open = "<< "; > > wrap.close = " >>"; > >What does this decorator "wrap"? A wrapper_decorator is one that only has open and close decoration values. Thus, it wraps the object associated with it (via a format object): template< class OutStream, typename T > OutStream & write( OutStream & os, const T & elem ) { return( os << open << elem << close ); } The sequence_decorators< char > type extends the wrapper_decorator< char > type, adding the separator property. > > == Cascading Style Sheets > > > > HTML provides a <style> tag to specify styling across the document >without > > linking to an external file, e.g.: > > <style>h1{ color: orange; font-size: 2pc; }</style> > > > > The equivalent within my library would be to define the styling on a > > stream, e.g.: > > > > std::cout > > << css::element( "pair" ) > > [ > > ( css::attribute( "open" ) = "<< " ) > > + ( css::attribute( "close" ) = " >>" ) > > ] > > << css::element( "container" ) > > [ > > css::attribute( "separator" ) = " | " > > ] > > << io::object( ob ) // output: [ << a, 5 >> | << b, -1 >> ] > > << css::element( "pair" ) > > [ > > css::attribute( "separator" ) = " = " > > ] > > << io::object( ob ); // output: [ << a = 5 >> | << b = -1 >> ] > >I'm sorry, but I'm worried of the direction you took. For me, the primary >utility of this library is debugging output. For that, I'd be happy with a >single style, as long as it's something usable, like YAML >(http://www.yaml.org/) I haven't implemented CSS functionality yet. It is my thoughts based on the comments by Jonathan. >I agree that you might want to store and then restore STL container from a >file, and the library addresses this need to. But I don't understand why >you would want to customize the formatting style. Basically, you either >should >the data to user, or not. In first case, you need a single usable style. >For >the second case, you might need another "compact" style. I don't see the >point of customization. It is currently possible to state what style formatting an object takes using the decorate function (format in the review implementation). Thus: // review implementation: std::cout << io::formatob( vec ).format( "( ", " )" ); // ( a, b, c, d ) Here, the separator is not set and thus takes the default value (the one provided by one of the mechanisms outlined above). You might want to customize formatting for various reasons. One example is if you have: std::list< std::string > names; and want to write that out as a HTML ordered list. You can do the following: std::cout << io::formatob( names ).format( "<ol><li>", "</li></ol>", "</li><li>" ); The examples provided in the library show some advanced formatting that can be achieved. >Finally, is this library going to be used for producing generic text files? >E.g. code generation. I think no, to generate text you need some text >template system, and that's way beyond the scope of the library. It is possible to do this to a limited degree, for example, outputting 4, 7, 10, -5 27, 11, 5, 17 ... so the data can be read in by a spreadsheet, for example. It is also possible to provide a basic form of message localization, reading a std::map< std::string, std::string > in from a file. E.g.: english.loc "goodnight" = "Good night. Sweet dreams." "..." = "..." german.loc "goodnight" = "Gute nacht. Sussen Schlafen." "..." = "..." spanish.loc "goodnight" = "Buenos noches." "..." = "..." portuguese.loc "goodnight" = "Boa noite." "..." = "..." int main( ... ) { std::ifstream loc( argv[ 1 ]); std::map< std::string, std::string > messages; loc >> io::formatob( messages, io::containerfmt( io::pairfmt ( io::containerfmt().format( "\"", "\"", "" ), // currently unsupported io::containerfmt().format( "\"", "\"", "" ) // currently unsupported ).format( " = " )) ).format( "", "\n[end]", "\n" ); std::cout << "goodnight = " << messages[ "goodnight" ] << '\n'; } >So, I'm not convinced custom style gives you anything. On the other hand, >it >will cost a lot. At the very least, even documenting the above will be >considerable effort. And given that the library is header-only, this >features >will cost everyone extra compile time. Even is 'css' stuff is in separate >header, you'd need the hooks for customization. Custom styling is currently implemented and is relatively cheap. The CSS design proposal is - I agree - complex in nature and would give a performance penalty. I was discussing a possible implementation to Jonathan's proposal. Regards, Reece _________________________________________________________________ Want to block unwanted pop-ups? Download the free MSN Toolbar now! http://toolbar.msn.co.uk/

2 1