- Boost - lists.boost.org

[config] boost::ulong_long_type issue for Borland 5.6.4?
by Gennaro Prota 29 Aug '08

29 Aug '08

John, is BOOST_HAS_LONG_LONG correctly defined for Borland 5.6.4? Many test failures seem related to this (I'm referring to trunk). Thanks, -- Genny

2 1

Re: [boost] String Algorithms Library: Case insensitive compareUTF-8
by Graham 28 Aug '08

28 Aug '08

>> Martin Lutken wrote: >>> Anyone who knows how this could be made possible? >>> I suppose I need a locale facet like the std::ctype, but which works for >>> UTF-8, and not just for ASCII a-z,A-Z. I guess the information in a >table >>> like this (http://www.unicode.org/Public/UNIDATA/CaseFolding.txt) >>> could be used. >>> >> >> This might not work out-of-the-box. StringAlgo lib is designed around the >sequences >> od characters. Since UTF-8 have variable character with encoding, >algotrithms >> in the library would not work as expected. >> >> To make it working, you will need a container with iterators, that will >> iterate over meta-characters, not bytes. >> >>> If it's better/easier just to convert the string to UTF-32 before doing >case >>> insensitive compares, replaces I could live with that. >> >> If you meant UTS-32 and you have a corresponding locale implementation, >than >> this approach is a viable solution. >> >> Sorry, what is UTS-32 ? I tried to Google it: 351 results, with none of >them >> looking like char encoding related. >> >> I found this article on Wikipedia on UTF-32/UCS-4: >> http://en.wikipedia.org/wiki/UTF-32 >> >> Is it not what I need ? >> I suspect that many people must have ran into similar problems. Perhaps >we should >> add a 32 bit string class to Boost. And until I get a better >understanding, I will >> keep calling it UTF-32 :-) >> > > >Sorry, I mixed up it a little. I meant UCS-4 a.k.a fixed-width encoding. I >was not >aware that UTF-32 id de-facto the same. > >Anyway, the statement about usability with StringAlgo still holds. It can >work with >any fixed-size encoding, as long as you have the corresponding locales. > >It could theoretically work also with variable-with characters, provided >you >have a container/localte framework, that allows to operate on >metacharacters. >I'm not sure how efficient it will be, though. > >Best regards, >Pavol. MArtin, The Unicode library I posted in the vault will do what you want for arbitrary characters. It allows you to take two UTF-32 unicode strings and compare them at different comparison levels [e.g. exact, case insensitive etc], and includes the calls necessary for iterating characters [which may be more than a single 4 byte character [e.g. surrogates can be 3 x 'UTF-32' numbers] and then of course the ability to iterate graphemes. It will allow you to do a case insensitive comparison using the full Unicode character library specification. The only thing we did not have time to do was do the string wrapper class. Feel free to work on that ! Thanks. Yours, Graham

1 0

FSM Review
by Phil Endecott 28 Aug '08

28 Aug '08

Rather than repeating myself too much here I refer the review manager to my two previous posts where I implemented a couple of simple problems using this library. My initial expectation was that I would find the library useful for these problems, but it became clear that the resulting code was no better than an ad-hoc implementation without the use of the library. I was hoping that in the time since then the author or some other reviewer would produce an example that would convince me that there are classes of problems where this library is useful, but no such example has appeared. > What is your evaluation of the design? The main mode of use of this library doesn't seem to offer enough beyond what's possible with a more ad-hoc implementation style to be worthwhile. I note that it also has a more declarative mode (with a state transition table) which I did not evaluate properly. > What is your evaluation of the implementation? I have not evaluated the implementation. > What is your evaluation of the documentation? It is sufficient. > What is your evaluation of the potential usefulness of the library? I have not been convinced that this library is useful. > Did you try to use the library? With what compiler? Did you have any > problems? I did not try to compile any of my code. > How much effort did you put into your evaluation? A glance? A quick reading? > In-depth study? A few hours. > Are you knowledgeable about the problem domain? Not especially. Actually in a previous life I knew a lot about implementing and optimising FSMs in hardware, but that doesn't really have a lot to do with most software implementations. > And, finally, every review should answer this question: Do you think the library should be accepted as a Boost library? No, not unless some convincing examples of applications where it is useful can be produced. Regards, Phil.

1 0

Re: [boost] UTF-8 conversion etc. (Sebastian Redl) (Sebastian Redl)
by Graham 28 Aug '08

28 Aug '08

>> As I said to Phil, Rogier and I completed a Unicode character library >> for >> >> Release under boost, but never submitted it to Boost as we had intended >> to >> >> release it with a string library built on it, and never had time to do >> the >> >> second part of the work. >> >Post it, and we'll do the second part. It's open-source. > >Sebastian Sebasian, As requested, I have posted a Unicode character support library in the boost vault as Unicode_lib.zip. Please feel free to use this under the boost license. It would be great if somebody had the time to develop the existing character support to ad the string wrappers that we had intended to - but ran out of time doing. It should be well documented, but if you want any questions answered, please feel free to ask and I'll try and help! Thanks. Yours, Graham

6 7

Another website docpage nit
by Jonathan Biggar 28 Aug '08

28 Aug '08

In the page: http://www.boost.org/doc/tools.html the description of Wave says: A Standards conformant C/C++ preprocessor usable on top of any other compiler. Usable for instance for the debugging of the expansion of macros in your code or as a replacement for your build in preprocessor. ^^^^^^ built- -- Jon Biggar Floorboard Software jon(a)floorboard.com jon(a)biggar.org

2 1

[smart_ptr] release()
by Phil Bouchard 28 Aug '08

28 Aug '08

As it turns out I think a release() member function should be added to the smart pointer. Its purpose is to give away ownership of the object. See the following pseudo-code: template <typename T> class smart_ptr { ... smart_ptr(element_type *); value_type * get(); element_type * release() { element_type * __p = pointer_ref(); pointer_ref() = 0; if (-- counter_ref()) return 0; else return __p; } }; It follows the same idea of its predecessor auto_ptr<> but will return a null pointer if the object is still shared thus not ready to be deleted. This way the allocator will be much easier to support either by calling this function before deallocate(), inside it or by using a specialized wrapper class to handle it: template <typename T> class allocator { ... typedef smart_ptr<T> pointer; void deallocate(pointer & __p) { delete p.release(); } }; -Phil

1 0

Website documentation page nit
by Jonathan Biggar 28 Aug '08

28 Aug '08

The docuemntation page on the website: http://www.boost.org/doc/ only has two subbullets (Boost Jam and Boost Build) under the "Tools" bullet. But if you click on the Tools bullet, you get a longer list: Boost.Build Boost.Jam Regression Inspect BoostBook bcp QuickBook Wave Shouldn't those all appear on the doc page. It took me a while to find the BoostBook documentation because of this. -- Jon Biggar Floorboard Software jon(a)floorboard.com jon(a)biggar.org

1 0

[next release] Any new libraries ready for the next release?
by Beman Dawes 27 Aug '08

27 Aug '08

Will any new libraries be ready to go in the next release? --Beman

10 17

[Boost][spirit] Broken nightly tests
by K. Noel Belcourt 27 Aug '08

27 Aug '08

Hi, The nightly tests are dying with the error from, apparently, the spirit library. Please refer to the Boost.Regex documentation for more information (don't panic: this is a strictly optional feature). error: Unable to find file or target named error: 'qi/confix.cpp' error: referred from project at error: '../libs/spirit/test' Thanks. -- Noel Belcourt

2 1

[filesystem] Boost 1.36 issue on Win64
by Noman_Khan＠elixir.com 27 Aug '08

27 Aug '08

Hi all I am trying to use Boost library on 64 bit windows and it is crashing whenever i call a boost function. I am using boost 1.36 with VS2008 and i have used the bellow line to compile boost's 64 bit version. bjam debug release threading=multi --toolset=msvc-9.0 architecture=x86 address-model=64 I am using BOOST_ALL_DYN_LINK preprocessor to link to boost. It crashes after saying that heap may be corrupted. Also it works fine if compiled for 32 bit windows. Here is a sample code that replicates the issue: /********************************************/ #include "boost/filesystem.hpp" int wmain(int argc, wchar_t* argv[]) { wchar_t path[] = L"c:/temp/test"; if(boost::filesystem::exists(path) ) { printf("Path exists.\n"); } else { printf("Path does not exists.\n"); } return 0; } /********************************************/ Here is the call stack at the time of the crash. > msvcr90d.dll!_CrtIsValidHeapPointer(const void * pUserData=0x00000000005e9780) Line 2103 C++ msvcr90d.dll!_free_dbg_nolock(void * pUserData=0x00000000005e9780, int nBlockUse=1) Line 1317 + 0xa bytes C++ msvcr90d.dll!_free_dbg(void * pUserData=0x00000000005e9780, int nBlockUse=1) Line 1258 + 0xe bytes C++ msvcr90d.dll!operator delete(void * pUserData=0x00000000005e9780) Line 54 + 0x12 bytes C++ msvcp90d.dll!std::allocator<unsigned short>::deallocate(unsigned short * _Ptr=0x00000000005e9780, unsigned __int64 __formal=16) Line 147 C++ msvcp90d.dll!std::basic_string<unsigned short,std::char_traits<unsigned short>,std::allocator<unsigned short> >::_Tidy(bool _Built=true, unsigned __int64 _Newsize=0) Line 2168 C++ msvcp90d.dll!std::basic_string<unsigned short,std::char_traits<unsigned short>,std::allocator<unsigned short> >::~basic_string<unsigned short,std::char_traits<unsigned short>,std::allocator<unsigned short> >() Line 916 + 0xf bytes C++ BoostTest.exe!boost::filesystem::exists<boost::filesystem::basic_path<std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t> >,boost::filesystem::wpath_traits> >(const boost::filesystem::basic_path<std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t> >,boost::filesystem::wpath_traits> & ph={...}) Line 292 C++ BoostTest.exe!boost::filesystem::exists(const boost::filesystem::basic_path<std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t> >,boost::filesystem::wpath_traits> & ph={...}) Line 626 + 0x2d bytes C++ BoostTest.exe!wmain(int argc=1, wchar_t * * argv=0x00000000005c9340) Line 9 + 0x1a bytes C++ BoostTest.exe!__tmainCRTStartup() Line 579 + 0x19 bytes C BoostTest.exe!wmainCRTStartup() Line 399 C Best Regards M. Noman Khan

3 3