July 2005 - Boost - lists.preview.boost.org

Boost Inspection Report, Run Date: 14:47:50 UTC, Saturday 30 July 2005
by Rene Rivera 30 Jul '05

30 Jul '05

[being run on the branch until release] http://www.boost.org/regression-logs/inspection_report.html -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org Boost Inspection Report *Run Date:* 14:47:50 UTC, Saturday 30 July 2005 An inspection program <http://www.boost.org/tools/inspect/index.html> checks each file in the current Boost CVS for various problems, generating this web page as output. Problems detected include tabs in files, missing copyrights, broken URL's, and similar misdemeanors. Totals 10418 files scanned 822 directories scanned 188 problems reported problem counts: 114 files with invalid line endings 0 bookmarks with invalid characters 0 invalid urls 17 broken links 28 unlinked files 22 file names too long 0 files with tabs 7 violations of the Boost min/max guidelines Summary *Library* *Problems* algorithm <#algorithm> 1 boost-root <#boost-root> 3 build <#build> 6 date_time <#date_time> 5 iostreams <#iostreams> 116 iterator <#iterator> 7 libs <#libs> 2 numeric <#numeric> 3 program_options <#program_options> 1 regex <#regex> 1 regression <#regression> 33 serialization <#serialization> 2 test <#test> 7 type_traits <#type_traits> 1 Details algorithm libs/algorithm/string/doc/external_concepts.html: unlinked file boost-root index.htm: broken link: doc/html/date_time/date_time_io.html, broken link: doc/html/date_time/details.html#date_time.changes, broken link: doc/html/date_time/local_time.html build tools/build/v2/example/libraries/util/foo/include/lib1.h: file's directory depth will exceed 8 levels if placed on a CD tools/build/v2/index.html: broken link: ../../../doc/html/bbv2.html, broken link: ../../../doc/html/bbv2/installation.html, broken link: doc/userman.pdf tools/build/v2/test/test_system.html: unlinked file date_time boost/date_time/date_parsing.hpp: violation of Boost min/max guidelines on line 80, violation of Boost min/max guidelines on line 81 boost/date_time/period.hpp: violation of Boost min/max guidelines on line 325, violation of Boost min/max guidelines on line 326 libs/date_time/xmldoc/date_time_docs_howto.html: unlinked file iostreams libs/iostreams/doc/acknowledgments.html: invalid (cr only) line-ending, unlinked file libs/iostreams/doc/bibliography.html: invalid (cr only) line-ending libs/iostreams/doc/classes/aggregate.html: invalid (cr only) line-ending libs/iostreams/doc/classes/array.html: invalid (cr only) line-ending libs/iostreams/doc/classes/back_inserter.html: invalid (cr only) line-ending libs/iostreams/doc/classes/bzip2.html: invalid (cr only) line-ending libs/iostreams/doc/classes/chain.html: invalid (cr only) line-ending libs/iostreams/doc/classes/char_traits.html: invalid (cr only) line-ending libs/iostreams/doc/classes/classes.html: invalid (cr only) line-ending libs/iostreams/doc/classes/code_converter.html: invalid (cr only) line-ending libs/iostreams/doc/classes/counter.html: invalid (cr only) line-ending libs/iostreams/doc/classes/device.html: invalid (cr only) line-ending libs/iostreams/doc/classes/file.html: invalid (cr only) line-ending libs/iostreams/doc/classes/file_descriptor.html: invalid (cr only) line-ending libs/iostreams/doc/classes/filter.html: invalid (cr only) line-ending libs/iostreams/doc/classes/filtering_stream.html: invalid (cr only) line-ending libs/iostreams/doc/classes/filtering_streambuf.html: invalid (cr only) line-ending libs/iostreams/doc/classes/gzip.html: invalid (cr only) line-ending libs/iostreams/doc/classes/line_filter.html: invalid (cr only) line-ending libs/iostreams/doc/classes/mapped_file.html: invalid (cr only) line-ending libs/iostreams/doc/classes/mode.html: invalid (cr only) line-ending libs/iostreams/doc/classes/newline_filter.html: invalid (cr only) line-ending libs/iostreams/doc/classes/null.html: invalid (cr only) line-ending libs/iostreams/doc/classes/regex_filter.html: invalid (cr only) line-ending libs/iostreams/doc/classes/stdio_filter.html: invalid (cr only) line-ending libs/iostreams/doc/classes/symmetric_filter.html: invalid (cr only) line-ending libs/iostreams/doc/classes/zlib.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/bidirectional_device.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/bidirectional_filter.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/blocking.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/closable.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/concepts.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/device.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/direct.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/dual_use_filter.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/filter.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/flushable.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/input_filter.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/localizable.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/multi-character.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/multi_character.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/optimally_buffered.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/output_filter.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/peekable.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/pipable.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/seekable_device.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/seekable_filter.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/sink.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/source.html: invalid (cr only) line-ending libs/iostreams/doc/concepts/symmetric_filter.html: invalid (cr only) line-ending libs/iostreams/doc/faq.html: invalid (cr only) line-ending libs/iostreams/doc/functions/close.html: invalid (cr only) line-ending libs/iostreams/doc/functions/combine.html: invalid (cr only) line-ending libs/iostreams/doc/functions/compose.html: invalid (cr only) line-ending libs/iostreams/doc/functions/copy.html: invalid (cr only) line-ending libs/iostreams/doc/functions/filter_test.html: invalid (cr only) line-ending libs/iostreams/doc/functions/flush.html: invalid (cr only) line-ending libs/iostreams/doc/functions/functions.html: invalid (cr only) line-ending libs/iostreams/doc/functions/get.html: invalid (cr only) line-ending libs/iostreams/doc/functions/imbue.html: invalid (cr only) line-ending libs/iostreams/doc/functions/invert.html: invalid (cr only) line-ending libs/iostreams/doc/functions/optimal_buffer_size.html: invalid (cr only) line-ending libs/iostreams/doc/functions/positioning.html: invalid (cr only) line-ending libs/iostreams/doc/functions/put.html: invalid (cr only) line-ending libs/iostreams/doc/functions/putback.html: invalid (cr only) line-ending libs/iostreams/doc/functions/read.html: invalid (cr only) line-ending libs/iostreams/doc/functions/restrict.html: invalid (cr only) line-ending libs/iostreams/doc/functions/seek.html: invalid (cr only) line-ending libs/iostreams/doc/functions/tee.html: invalid (cr only) line-ending libs/iostreams/doc/functions/write.html: invalid (cr only) line-ending libs/iostreams/doc/guide/asynchronous.html: invalid (cr only) line-ending libs/iostreams/doc/guide/buffering.html: invalid (cr only) line-ending libs/iostreams/doc/guide/code_conversion.html: invalid (cr only) line-ending libs/iostreams/doc/guide/concepts.html: invalid (cr only) line-ending libs/iostreams/doc/guide/convenience.html: invalid (cr only) line-ending, unlinked file libs/iostreams/doc/guide/exceptions.html: invalid (cr only) line-ending libs/iostreams/doc/guide/filtering_streams.html: invalid (cr only) line-ending libs/iostreams/doc/guide/generic_streams.html: invalid (cr only) line-ending libs/iostreams/doc/guide/guide.html: invalid (cr only) line-ending libs/iostreams/doc/guide/lifetimes.html: invalid (cr only) line-ending libs/iostreams/doc/guide/modes.html: invalid (cr only) line-ending libs/iostreams/doc/guide/pipelines.html: invalid (cr only) line-ending libs/iostreams/doc/guide/text_processing.html: invalid (cr only) line-ending libs/iostreams/doc/guide/traits.html: invalid (cr only) line-ending libs/iostreams/doc/guide/views.html: invalid (cr only) line-ending libs/iostreams/doc/home.html: invalid (cr only) line-ending libs/iostreams/doc/index.html: invalid (cr only) line-ending libs/iostreams/doc/installation.html: invalid (cr only) line-ending libs/iostreams/doc/macros/buffer_sizes.html: invalid (cr only) line-ending libs/iostreams/doc/macros/macros.html: invalid (cr only) line-ending libs/iostreams/doc/macros/workarounds.html: invalid (cr only) line-ending libs/iostreams/doc/menu.html: invalid (cr only) line-ending libs/iostreams/doc/portability.html: invalid (cr only) line-ending libs/iostreams/doc/quick_reference.html: invalid (cr only) line-ending libs/iostreams/doc/rationale.html: invalid (cr only) line-ending, unlinked file libs/iostreams/doc/reference.html: invalid (cr only) line-ending libs/iostreams/doc/tree/tree.css: invalid (cr only) line-ending libs/iostreams/doc/tutorial/container_device.html: invalid (cr only) line-ending libs/iostreams/doc/tutorial/container_sink.html: invalid (cr only) line-ending libs/iostreams/doc/tutorial/container_source.html: invalid (cr only) line-ending libs/iostreams/doc/tutorial/dictionary_filters.html: invalid (cr only) line-ending libs/iostreams/doc/tutorial/dual_use_filters.html: invalid (cr only) line-ending libs/iostreams/doc/tutorial/filter_usage.html: invalid (cr only) line-ending libs/iostreams/doc/tutorial/finite_state_filters.html: invalid (cr only) line-ending libs/iostreams/doc/tutorial/line_wrapping_filters.html: invalid (cr only) line-ending libs/iostreams/doc/tutorial/multichar_filters.html: invalid (cr only) line-ending libs/iostreams/doc/tutorial/shell_comments_filters.html: invalid (cr only) line-ending libs/iostreams/doc/tutorial/tab_expanding_filters.html: invalid (cr only) line-ending libs/iostreams/doc/tutorial/tutorial.html: invalid (cr only) line-ending libs/iostreams/doc/tutorial/unix2dos_filters.html: invalid (cr only) line-ending libs/iostreams/doc/tutorial/writing_devices.html: invalid (cr only) line-ending libs/iostreams/doc/tutorial/writing_filters.html: invalid (cr only) line-ending libs/iostreams/test/putback_test.hpp: invalid (cr only) line-ending iterator libs/iterator/doc/filter_iterator_ref.html: unlinked file libs/iterator/doc/indirect_iterator_ref.html: unlinked file libs/iterator/doc/issues.html: unlinked file libs/iterator/doc/iter-issue-list.html: unlinked file libs/iterator/doc/iterator_adaptor_ref.html: unlinked file libs/iterator/doc/make_filter_iterator.html: unlinked file libs/iterator/doc/ref_problem.html: unlinked file libs libs/libraries.htm: broken link: ../doc/boost.docbook, broken link: ../doc/boost.fo numeric boost/numeric/conversion/detail/old_numeric_cast.hpp: violation of Boost min/max guidelines on line 159, violation of Boost min/max guidelines on line 192 libs/numeric/conversion/doc/converter_policies.html: invalid (cr only) line-ending program_options boost/program_options/positional_options.hpp: violation of Boost min/max guidelines on line 43 regex libs/regex/performance/input.html: unlinked file regression regression/.htaccess: leading character of one of the path compontents is not alphabetic, nonportable path tools/regression/test/compile-fail~fail.cpp: nonportable path tools/regression/test/compile-fail~pass.cpp: nonportable path tools/regression/test/compile~fail.cpp: nonportable path tools/regression/test/compile~pass.cpp: nonportable path tools/regression/test/compile~warn.cpp: nonportable path tools/regression/test/run-fail~compile-fail.cpp: nonportable path tools/regression/test/run-fail~fail-warn.cpp: nonportable path tools/regression/test/run-fail~fail.cpp: nonportable path tools/regression/test/run-fail~pass.cpp: nonportable path tools/regression/test/run-fail~warn.cpp: nonportable path tools/regression/test/run~compile-fail.cpp: nonportable path tools/regression/test/run~fail-note.cpp: nonportable path tools/regression/test/run~fail-warn.cpp: nonportable path tools/regression/test/run~fail.cpp: nonportable path tools/regression/test/run~note.cpp: nonportable path tools/regression/test/run~pass.cpp: nonportable path tools/regression/test/run~warn-note.cpp: nonportable path tools/regression/test/run~warn.cpp: nonportable path tools/regression/xsl_reports/runner/instructions.html: unlinked file tools/regression/xsl_reports/xsl/html/issues_legend.html: unlinked file tools/regression/xsl_reports/xsl/html/library_developer_legend.html: unlinked file tools/regression/xsl_reports/xsl/html/library_user_legend.html: unlinked file tools/regression/xsl_reports/xsl/html/make_tinyurl.html: unlinked file tools/regression/xsl_reports/xsl/html/summary_developer_legend.html: unlinked file tools/regression/xsl_reports/xsl/html/summary_user_legend.html: unlinked file tools/regression/xsl_reports/xsl/v2/html/issues_legend.html: unlinked file tools/regression/xsl_reports/xsl/v2/html/library_developer_legend.html: unlinked file tools/regression/xsl_reports/xsl/v2/html/library_user_legend.html: unlinked file tools/regression/xsl_reports/xsl/v2/html/make_tinyurl.html: unlinked file tools/regression/xsl_reports/xsl/v2/html/summary_developer_legend.html: unlinked file tools/regression/xsl_reports/xsl/v2/html/summary_user_legend.html: unlinked file serialization libs/serialization/doc/serialization.html: broken link: ../../../boost/serialization/shared_count.hpp libs/serialization/vc7ide/test_reset_object_address.vcproj: filename > 31 chars test libs/test/doc/components/test_exec_monitor/compilation.html: broken link: ../../../src/supplied_log_formatters.cpp, broken link: ../../../src/unit_test_result.cpp libs/test/doc/components/utf/compilation.html: broken link: ../../../src/supplied_log_formatters.cpp, broken link: ../../../src/unit_test_result.cpp libs/test/doc/components/utf/components/test_case/boost_function_tc.html: broken link: ../../../../../../../boost/test/unit_test_suite_ex.hpp libs/test/doc/components/utf/components/test_case/param_boost_function_tc.html: broken link: ../../../../../../../boost/test/unit_test_suite_ex.hpp libs/test/doc/tests/unit_test_suite_ex_test.html: broken link: ../../test/unit_test_suite_ex_test.cpp type_traits libs/type_traits/cxx_type_traits.htm: unlinked file

2 1

Re: [boost] Call for interest for native unicode character and string support in boost - updated definition
by Graham 30 Jul '05

30 Jul '05

Hi, I enclose a new set of headers, put in one file for convenience. I have tried to enable the use of iterators and templates where possible but still allow the use of the functions by third party DLLs requiring sharing of source code and class definitions. This makes the use of iterators interesting. I look forward to any comments or ideas on how better to do this first/ third party compromise. Yours, Graham Barnett BEng, MCSD/ MCAD .Net, MCSE/ MCSA 2003, CompTIA Sec+

3 2

[repost][getting started][serialization] outdated info about Boost.Serialization
by JOAQUIN LOPEZ MU?Z 30 Jul '05

30 Jul '05

I think this msg might have went unnoticed, so allow me to repost it: Hello, the section on autolinking in the getting started page, as it appears in http://boost-consulting.com/boost/more/getting_started.html#auto-link states that Boost.Serialization is not autolinkable nor dynamically linkable. I think this is no longer true starting with Boost 1.33. If so, maybe the release manager will accept that this bit be changed before packing up (I can't do the change myself, though.) Joaquín M López Muñz Telefónica, Investigación y Desarrollo

1 0

Re: [boost] Call for interest for native unicode character and string support in boost
by Graham 30 Jul '05

30 Jul '05

>Date: Thu, 28 Jul 2005 06:24:52 +0200 >From: Rogier van Dalen <rogiervd(a)gmail.com> > >Hi Graham, > >> In my experience this is handled by the dictionary pass [outside the >> scope of this support] adding special break markers into the text [which >> need to be supported transparently as Unicode characters that happen to >> be in the private use range at this level] so that the text and string >> iterators can then be handled normally. The fact that the break markers >> are special characters in the private use range should not be relevant >> or special at this level. > >You mean that we invent a set of private characters that the >dictionary pass should use? Actually individual developers are free to use their own private range as they see fit - these characters are just one example of the use of non standard private characters - 'we' as in boost do not invent these - any developer can add these characters to their own code to handle Thai if private character definition on a per-developer instance is supported. >> We must provide a Unicode character system on which all libraries can >> operate consistently. >> >> Even working out a grapheme break may require different sets of >> compromises that must work consistently for any set of inter-related >> libraries to be successful. > >Do you have an example? I'm having trouble envisioning a situation in >which libraries based on different Unicode versions actually cause >conflicts. I enclose a few of the Unicode 4.0.1 to 4.1 differences as an example Notable Changes From Unicode 4.0.1 to Unicode 4.1.0 * Addition of 1273 new characters to the standard, including those to complete roundtrip mapping of the HKSCS and GB 18030 standards, five new currency signs, some characters for Indic and Korean, and eight new scripts. (The exact list of additions can be seen in DerivedAge.txt, in the age=4.1 section.) * Change in the end of the CJK Unified Ideographs range from U+9FA5 to U+9FBB, with the addition of some Han characters. The boundaries of such ranges are sometimes hardcoded in software, in which case the hardcoded value needs to be changed. >> This is actually a very difficult thing to do due to limitations in the >> Windows GDI scaling [which is not floating point but 'rounds' scaling >> calculations, and which can result in as much as a +/-10% difference in >> simple string lengths on different machines, unless handled specifically >> e.g. IIIIIIIIIIIIIIII can be the same length as WXWXWX on one machine >> but there can be a 20% difference on another machine] and requires >> access to the data conversion mechanisms and requires that you know how >> you are going to perform the rendering. > >I fear I don't understand what you mean. It sounds to me like you're >suggesting defining a new font format for the Boost Unicode library. Please accept that there are fundamental issues with the way in which scaling happens on a Windows platform that means that anybody who want to ensure that there are the same number of lines shown in a document regardless of the 'zoom' setting used to display that document so that the lines appear to have the same relative lengths at any zoom setting have to work very hard. This might be an example of where a particular implementation might store an array of wrapped lines rather than an array of characters. By moving the Unicode specific rules out of, and separate to, the storage, the storage method becomes an implementation issue. There can then be many different storage methods based on the same Unicode rules, e.g. implementations based on vector<char32_t> and vector<char16_t> to give two examples. >> >Why would you want to do canonical decomposition explicitly in a >> >regular expression? >> >> Let me give two examples: >> >> First why? >> >> If you use a regular expression to search for <e acute> - [I use angle >> brackets <> to describe a single character for this e-mail] then >> logically you should find text containing: >And <acute> is a combining acute? Yes >> <e><acute> and <e acute> as these are both visually the same when >> displayed to the user. > >> Second why do we need to know? If we decompose arbitrarily then we can >> cover over syntax errors and act unexpectedly: >> [...] >Yes, the Unicode library should by default process grapheme clusters >rather than code points. This would automatically solve the regex >issue. I would envision that the string storage classes would support UTF16, UTF32 and grapheme based iterators. It is important in some circumstances to be able to process UTF32 characters rather than graphemes - for example when drawing the string ! As graphemes are can be several UTF32 characters long and require calculation to determine their data length it is often not practical to make these the default processing scheme. >> This private use character data would NOT be published or distributed - >> the facility to merge them in during usage allows each developer the >> access to add their own private use data for their own system only. > >But surely this means every app would have to come with a different DLL? >I'm not so sure about this. For many cases other markup (XML or >something) would do. Maybe other people have opinions about this? I propose making it so that the Unicode data could be either placed in a DLL or an application. The data and boost functions would be supplied as a number of .h and .cpps that can be compiled in to either. The functions would be in supplied .h and .cpps, and the data .h and .cpps would be generated once only by a developer using a stand alone command line application. Access to the Unicode data would ONLY be by using the set of core functions or function wrappers round the core functions as outlined in my previous attachment and these core functions would be accessed by function pointers which can therefore be passed across DLLs even when the DLLS are written by third parties. The DLLs could then ask for the Unicode function pointers if required during initialisation so that first and third party DLLs could work with the same data. Yours, Graham

2 1

Error on Front Page
by Joe Gottman 30 Jul '05

30 Jul '05

There's an embarrassing typo on the redesigned front page. Near the top it says "More Boost libraries will part of the upcoming TR2". You need to add a "be" after the "will". Also, isn't this sentence a bit presumptuous? As far as I know, no library has been accepted into the TR2, or even formally proposed. Maybe you should have an adverb like "probably" or "likely" somewhere in this sentence. Joe Gottman

3 2

Re: [boost] Interest in an ODBC library?
by JOAQUIN LOPEZ MU?Z 29 Jul '05

29 Jul '05

----- Mensaje original ----- De: Joaquin M Lopez Munoz <joaquin(a)tid.es> Fecha: Viernes, Julio 29, 2005 5:28 pm Asunto: Re: [boost] Interest in an ODBC library? > > template<typename Element> > void reverse_dump(IBidirectionalContainer<Element> i) > { > std::copy( > i.rbegin(),i.rend(), > std::ostream_iterator<Element>(std::cout)); > } Thinking about it some more, we could really use the version of reverse_dump in the static case also for the dynamic situation: template<typename Index> void reverse_dump(const Index& i) { std::copy( i.rbegin(),i.rend(), std::ostream_iterator<typename Index::value_type>(std::cout)); } In the dynamic case, reverse_dump would be then instantiated as reverse_dump<IBidirectionalContainer<Element> >. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

bjam stage forgot symlinks FIX BEFORE RELEASE
by Neal Becker 29 Jul '05

29 Jul '05

I just built from a recent cvs using: ICU_PATH=/usr ICU_LINK="-licuuc -licui18n" PYTHON_ROOT=/usr PYTHON_VERSION=2.3 bjam -sTOOLS=gcc stage I noticed that symlinks are missing. for each lib "x", in stage/lib there is libx.so.1.0.0 (actual binary) libx.so -> libx.so.1.0.0 (link) but there must be also libx.so.1 -> libx.so.1.0.0 This is because (I guess) soname of the library is set to libx.so.1, and when you link to libx then at runtime it will look for libx.so.1 (which it won't find)

2 2

Re: [boost] Interest in an ODBC library?
by Brian Braatz 29 Jul '05

29 Jul '05

Joaquin! Glad you responded and Good to be "talking" with you again :) Below: > On Behalf Of JOAQUIN LOPEZ MU?Z [Brian Braatz Writes:] > > > > I am not sure if he is still interested, but Joaquin Munez and I > > exchanged emails awhile back about collaborating on such a beast. > > > > The general idea was to take the functionality in multi-index > > containerand make it work dynamically. > > > [JOAQUIN LOPEZ MUNEZ Writes:] > I am still interested, and it is my plan to implement a > dynamic_multi_index_container in the future, if there's > interest in such a thing --serving as the foundation for > a DB table structure would be a very exciting application, > undoubtedly. > > Let me sketch what I have in mind: The part of adding/removing > indices at run time is not too hard: I haven't written any actual > code, but the design of that feature seems reasonably > straightforward to me. Some speed/space performance will > be lost, but I guess this is expected. > > The hard part, IMHO, is how to gain access to such indices. > Clearly some kind of runtime polymorhpisn is involved > for a dynamic_multi_index_container to have any use: > otherwise, the user code would have to know the exact type > of the index it is retrieving. So we need something more powerful > than the current static get<> interface. A possibility > is to retrieve indices by mean of *interfaces* as > defined in Jonathan Turkanis' BIL library: [Brian Braatz Writes:] If you would please elaborate. (some of us are "slower" than others :) ). is the problem getting to the index objects themselves via inherit_linearly? if you have dynamic data, then I am thinking you also have dynamically applied indices? Maybe I can elaborate- consider the following pseudo code: connection con = db.connect("myserver,root,password,mydatabase"); dynamic_table dt; // the select "*" means bring me back all the fields from that table // even though I don't know what the fields ARE yet dt = query("select * from person"); // ok so now dt has an UNKNOWN number of columns dt.add_index( index("first_name")); // or something along those lines. in this case, the index is applied dynamically. so how does that connect with the things you said ? Thanks, Brian

2 1

[pointer container] new libraries docs?
by David Abrahams 29 Jul '05

29 Jul '05

Why does pointer container appear in both the new and updated libraries section of the main page? -- Dave Abrahams Boost Consulting www.boost-consulting.com

2 1

[signals] making Assignable and CopyConstructable
by Rebooted 29 Jul '05

29 Jul '05

In my program I need to store a map of signals, with an integer id corresponding to a signal in the map. Objects can request to be informed when another a specific message is emitted by connecting a member function to the signal in this map at the index corresponding to that message type. However, since boost::signal inherits noncopyable, it cannot be stored in a map. What are the reasons for signal being noncopyable, and is there any chance this could be changed in the future?

4 3