- Boost-users - lists.boost.org

sockets/pipes
by Simmons, Aaron 21 Sep '04

21 Sep '04

Does Boost have named-pipes and/or sockets classes? If no... Are any in the works? Does anyone know of a good C++ pipes and/or sockets wrapper classes? Thanks, Aaron Simmons

2 1

RE: [Boost-users] sockets/pipes
by Richard Reitmeyer 20 Sep '04

20 Sep '04

I'd suggest ACE. Look for Douglas Schmidt's stuff at wustl. > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Simmons, Aaron > Sent: Monday, September 20, 2004 2:12 PM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] sockets/pipes > > > Does Boost have named-pipes and/or sockets classes? > > If no... Are any in the works? Does anyone know of a good C++ pipes > and/or sockets wrapper classes? > > > > Thanks, > Aaron Simmons > > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

1 0

RE: [Boost-users] Can boost::tokenizer tokenize 2byte character s tring?
by Rozental, Gennadiy 20 Sep '04

20 Sep '04

If it 2byte why are you using boost::char_separator<char>? Shouldn't you be using boost::char_separator<wchar_t>? Gennadiy. > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Lee, Joo-Young > Sent: Saturday, September 18, 2004 12:39 AM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] Can boost::tokenizer tokenize 2byte > character string? > > > Hi. > > I try to use 'boost::tokenizer<boost::char_separator<char> >' > to separate 2byte character string like Korean, Japanese, or Chinese. > > But, I found that it does not works correctly. > > Is there a solution? > > Thanks for the help, > > Lee Joo-Young > > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

2 1

RE: [Boost-users] Can boost::tokenizer tokenize 2byte character string?
by Ben Hutchings 20 Sep '04

20 Sep '04

Gennadiy Rozental <gennadiy.rozental(a)thomson.com> wrote: > If it 2byte why are you using boost::char_separator<char>? > > Shouldn't you be using boost::char_separator<wchar_t>? I think Lee Joo-Young is talking about multibyte strings in an encoding such as GB2312 and Shift_JIS that uses 1 or 2 bytes per character rather than wide strings that use a fixed 2 bytes per character on certain platforms (or rather, used to until UTF-16 came along). Ben.

1 0

RE: [Boost-users] Can boost::tokenizer tokenize 2byte character string?
by Ben Hutchings 20 Sep '04

20 Sep '04

Joo-Young Lee <trowind(a)gmail.com> wrote: > I try to use 'boost::tokenizer<boost::char_separator<char> >' > to separate 2byte character string like Korean, Japanese, or > Chinese. > > But, I found that it does not works correctly. > > Is there a solution? You should probably convert them to wide strings and use the wchar_t version instead. The standard C++ library and Boost libraries tend not to work well with multibyte encodings.

1 0

boost::serialization problem, derived class through shared_ptr
by Jedediah Smith 20 Sep '04

20 Sep '04

I'm trying to serialize a derived class through a shared_ptr<> to the base class. I'm getting an unregistered class exception even though my derived class is registered with register_type<>. It seems the exception is being thrown while trying to serialize boost::detail::sp_counted_base which I believe is part of shared_ptr. Could this be an internal error in the serialization library?

2 1

[boost-users][MPL] integral_c<long long,...>
by Cromwell Enage 19 Sep '04

19 Sep '04

The attached program fails to compile if BOOST_HAS_LONG_LONG is defined. The error is mainly about integral_rank<long long int> not having a static member named 'value'. Is integral_c not meant to be used with long long? Cromwell Enage __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail

2 2

Regex Libraries giving errors
by Corey M. Ellis 19 Sep '04

19 Sep '04

Hi, I am trying to use the regex library (regex_match in particular) I included "boost/regex.hpp". I get the following errors when compiling my code. g++ -W -Wall -Wpointer-arith -O3 -g -pipe -D_REENTRANT -DACE_HAS_AIO_CALLS -D_GNU_SOURCE -I/usr/local/ACE_wrappers -DACE_HAS_EXCEPTIONS -D__ACE_INLINE__ -I/usr/local/ACE_wrappers -I/usr/local/include -I/usr/local/include/boost-1_31 -DACE_NTRACE=1 -D__USE_REG_EXPR -c -o .obj/FTP_Task.o FTP_Task.cpp In file included from /usr/local/include/boost-1_31/boost/cregex.hpp:30, from /usr/local/include/boost-1_31/boost/regex/v4/regex.hpp:25, from /usr/local/include/boost-1_31/boost/regex.hpp:34, from FTP_Task.h:19, from FTP_Task.cpp:1: /usr/local/include/boost-1_31/boost/regex/v4/cregex.hpp:75: error: syntax error before numeric constant /usr/local/include/boost-1_31/boost/regex/v4/cregex.hpp:96: error: ISO C++ forbids declaration of `reg_comp_flags' with no type /usr/local/include/boost-1_31/boost/regex/v4/cregex.hpp:100: error: syntax error before numeric constant /usr/local/include/boost-1_31/boost/regex/v4/cregex.hpp:103: error: ISO C++ forbids declaration of `reg_exec_flags' with no type make[1]: *** [.obj/FTP_Task.o] Error 1 make[1]: Leaving directory `/home/bipuser/nBIP-9.0/src' make: *** [NBIP] Error 2 Can sme please shed some light on the problem. I am only using the regex_match function. I create an expression object, and use regex_match to match against it. Thanks in advance for any help. Corey

2 5

Re: [Boost-users] Regex Libraries giving errors
by corey.m.ellis＠comcast.net 19 Sep '04

19 Sep '04

Thanks for the quick response. Do you know of a workaround that is being used for version 1_31. All the examples say include "boost/regex.hpp". Is there some way I can include the headers so the problem will go away. What's really strange is that I compiled the entire library using the Jam method, and it I got these regex errors. I then compiled the regex libraries using the gcc make file, and use the static libraries when I compiled. It worked. But after I made some more code changes (not regex changes) to my application and recompiled, I started getting the errors again. I thought the gcc compilation fixed it, but it didn't. Anyway, if you could tell me a workaround that would be great. Is it just a matter of trying to include the regex.hpp header first before the regex.h header gets included, have other people seen this problem in the regex library? Corey -------------- Original message -------------- > > I am trying to use the regex library (regex_match in particular) > > I included "boost/regex.hpp". I get the following errors when compiling > > my code. > > > > Can sme please shed some light on the problem. I am only using the > > regex_match function. I create an expression object, and use regex_match > > to match against it. > > > > Thanks in advance for any help. > > I suspect that you are including the platforms (possibly > indirectly) before including . That currently causes > conflicts: there is a fix in the works, but it involves a complete > restructuring of Boost.Regex that won't be released until Boost-1.33 (that's > the release after next). > > John. > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

RE: [Boost-users] Boost problems
by Puverle, Tomas (IT) 18 Sep '04

18 Sep '04

> <snip> > Done, apologies for the delay, I didn't notice your message > first time around, I should have made the topic more obvious, like "Bug report: ... " or something. Would it have been better or made it easier for you if I had posted the original report to the boost developer forum? > Thanks for the bug report, > > John. Thank you very much John. Also, regarding the last issue mentioned in my original email (Boost.Build), should I cross post it to the Boost.Build forum? Thanks, Tom -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited.

2 1