headers
Sam Peterson | 1 Sep 02:34
Picon

subgraph and bundled properties

According to the release notes of version 1.33, bundled properties are
now supposed to work with the subgraph adapter.  I am currently using
1.34  However, I'm receiving a compiler error that I never was before
I tried to switch to the subgraph adapter:

graph.cpp:569:   instantiated from here
boost_1_34_1/boost/graph/properties.hpp:355: error: no type named
'vertex_bundled' in 'class boost::subgraph<boos\
t::adjacency_list<boost::setS, boost::vecS, boost::bidirectionalS,
Paper, boost::property<boost::edge_index_t, lo\
ng unsigned int, boost::no_property>, boost::no_property, boost::listS> >'

The line in question looks like this:

    put(&Paper::authors, *g,
        index_map.index_map[atoi(current_paper_id->c_str())], name_index);

My bundled properties and graph typdefs look like this:

struct Paper
{
  unsigned int paper_id;
  std::string title;
  std::vector<std::size_t> authors;
  std::string subject;
  std::string description;
  std::string publisher;
  std::string date_of_paper;
  std::string format;
  std::string identifier;
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jeffrey Jiang | 1 Sep 05:08
Picon
Picon

Re: using shared_array in Nd array

Thanks for the reply. I agree that this way is prob clearer and predictable.
However in this case I am implementing a fix size grid of pointers, to 
represent a geographical map, and the location of the pointer to determine 
the position of the character.

So although using vector in this case would work, it will convey a wrong 
message to the users that
-they can resize the grid
-the location of the pointer is not impt

I would rather use a shared_ptr<Character> **characterGrid instead, which 
bring us back to the problem below.

Jeffrey.

"James Emerton" <ephelon <at> gmail.com> wrote in message 
news:c9424d940708310855t3d5acd1boef1c2686bfabfca5 <at> mail.gmail.com...
> Do you really need to have a shared_array containing shared_ptrs?
>
> You would probably be better off with something like:
>
> std::vector< std::vector< boost::shared_ptr<Character> > > characterGrid;
> characterGrid.resize( _info.l );
> for( int i = 0; i < _info.l; ++i )
>  characterGrid.resize( _info.w );
>
> James
>
>
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Edward Diener | 1 Sep 08:24

Re: [Filesystem] Native Pathname Format

Hughes, James wrote:
>> -----Original Message-----
>> From: boost-users-bounces <at> lists.boost.org 
>> [mailto:boost-users-bounces <at> lists.boost.org] On Behalf Of 
>> Edward Diener
>> Sent: 31 August 2007 00:05
>> To: boost-users <at> lists.boost.org
>> Subject: [Boost-users] [Filesystem] Native Pathname Format
>>
>> I can not determine from the Filesystem documentation, nor 
>> the reference documentation which comes with it, what is the 
>> acceptable syntax for the native pathname format. It appears 
>> one must start the native pathname format with //: in order 
>> for it to be recognized, but I can not tell from what appears 
>> to me to be very confusing documentation whether this is so 
>> for the Boost Fileystem implementation. This would mean, 
>> let's say under Windows, that "c:\afile" would not be 
>> recognized but that "//:c:\afile" would be recognized, as far 
>> as I can make out from the documentation. It sure is confusing IMO.
>>
>> Can anybody clarify how this works for Filesystem and/or 
>> where there is a clear explanation of how it works in the 
>> documentation ?
> 
> Take a look at the code itself - it's pretty self explanatory. Native
> means precisely that - it uses the native OS format (which reading the
> code is windows or posix in 1.33 - see the checker functions)
> 
> Boost/filesystem/Path.hpp
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
dhruva | 1 Sep 16:52
Picon
Gravatar

A need for a COOKBOOK

Hi,
 I am trying to get more into BOOST than what I am using currently
(which is quite minimal compared to what BOOST has to offer these
days) and which does not include a whole lot of new things that have
got into BOOST.
 Are there any BOOST professionals willing to come up with a COOKBOOK
for using BOOST libraries? The book "Beyond the C++ Standard Library:
An Introduction to Boost" has a decent coverage but is quite dated
compared to the leap BOOST library suite has seen in the recent days.
 As a user of BOOST, I request someone with good knowledge to come up
with a COOKBOOK (like the PERL/PYTHON cookbook) for the benefit for
BOOST users. It could be modeled along the PYTHON COOKBOOK.
Activestate has a site to submit recipes and those are taken up,
polished and edited into a nice book.

with best regards,
dhruva

--

-- 
Dhruva Krishnamurthy
Contents reflect my personal views only!
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Permalink | Reply | 0 comments |
headers
Tommy Nordgren | 1 Sep 17:03
Picon

Failing to build dynamic regexp libraries on Mac OS X

Building dynamic regular experssion libraries fails on Mac OS X  
Tiger , when attempting to
link against ICU.
I would appreciate any hint on how to fix this.
All the ICU libraries are present in /usr/local/lib,
so I wonder if I need to add -licudata to the build somehow. (As can  
be seen from the build log,
only -licui18n and  -licuuc are added to the command line. (I've  
tried to edit the boost distribution files
that refer to theese flags, to also include -icudata , but the  
command line passed to the tools don't change,
so how do I do it)

./tools/jam/src/bin.macosxppc/bjam -sICU_PATH=/usr/local --user- 
config=user-config.jam
Building Boost.Regex with Unicode/ICU support enabled
Using ICU in /usr/local/include
...patience...
...patience...
...found 4691 targets...
...updating 4 targets...
darwin.link.dll bin.v2/libs/regex/build/darwin/release/threading- 
multi/libboost_regex-mt-1_34_1.dylib
ld: warning can't open dynamic library: libicudata.36.dylib  
referenced from: /usr/local/lib/libicui18n.dylib (checking for  
undefined symbols may be affected) (No such file or directory, errno  
= 2)
ld: Undefined symbols:
_icudt36_dat referenced from libicuuc.36 expected to be defined in  
libicudata.36.dylib
(Continue reading)

Permalink | Reply | 2 comments |
headers
Gernot Vormayr | 1 Sep 17:46
Picon

boost::any typeid and different modules

Hi!

I have some problems using boost::any in different modules that get 
loaded with libdl. If i store an int in the boost::any it works like a 
charm - but when i use a std::string then the boost::any (holding a 
std::string) isn't any_castable to a std::string because it seems that 
typeid(std::string) != boost::any.type(). Only thing which is the same 
is the string represantation of type().name().

I came around this with my own any_cast implementation:

     template<typename ValueType>
     ValueType * any_cast(any * operand)
     {
         return operand &&
           (operand->type() == typeid(ValueType) || 
std::string(operand->type().name()).compare(typeid(ValueType).name())==0)
                     ? &static_cast<any::holder<ValueType> 
*>(operand->content)->held
                     : 0;
     }

Is there a better way to address this issue?

Best regards,
Gernot Vormayr
Permalink | Reply | 2 comments |
headers
John Maddock | 1 Sep 18:27
Picon

Re: Failing to build dynamic regexp libraries on Mac OS X

Tommy Nordgren wrote:
> Building dynamic regular experssion libraries fails on Mac OS X
> Tiger , when attempting to
> link against ICU.
> I would appreciate any hint on how to fix this.
> All the ICU libraries are present in /usr/local/lib,
> so I wonder if I need to add -licudata to the build somehow. (As can
> be seen from the build log,
> only -licui18n and  -licuuc are added to the command line. (I've
> tried to edit the boost distribution files
> that refer to theese flags, to also include -icudata , but the
> command line passed to the tools don't change,
> so how do I do it)

Try:

bjam -sHAVE_ICU=1 linkflags=-licudata

Let me know if that fixes things, and then I'll update the build script 
accordingly.

HTH, John.
Permalink | Reply | 1 comment |
headers
Mark Ruzon | 2 Sep 00:58
Picon

Re: [multi_array] Warnings on upgrade to 1.34.1

Ronald Garcia <garcia <at> cs.indiana.edu> writes:

> 
> Hi Mark,
> 
> Here's an experiment for you:
> 
> Could you try changing the line below to:
> disable_if<typename boost::is_integral<BaseList>,void >::type
> 

I tried your fix, Ron, and it didn't change the error at all.  Any other
suggestions?

Thanks,
Mark Ruzon
Permalink | Reply | 0 comments |
headers
Joel de Guzman | 2 Sep 01:55
Picon
Favicon

Re: Spirit 1.8.5 and 1.6.4 released

Nicola Musatti wrote:
> It is my pleasure to announce the release of Spirit 1.8.5 and 1.6.4 .
> 
[...]

Woohoo! Great :-) Thank you Nicola. You're DA MAN. I'll update the
website now.

Regards,
--

-- 
Joel de Guzman
http://www.boost-consulting.com
http://spirit.sf.net

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
Permalink | Reply | 0 comments |
headers
Stephan Diederich | 2 Sep 02:21
Gravatar

Re: boost::any typeid and different modules

Hi Gernot,

On 9/1/07, Gernot Vormayr <gernot.vormayr <at> student.tuwien.ac.at> wrote:
Hi!

I have some problems using boost::any in different modules that get
loaded with libdl. If i store an int in the boost::any it works like a
charm - but when i use a std::string then the boost::any (holding a
std::string) isn't any_castable to a std::string because it seems that
typeid(std::string) != boost::any.type(). Only thing which is the same
is the string represantation of type().name().

I've recently encountered this issue, too. The comparison failes because it compares pointers and each module has its own static rtti information. You could try http://lists.boost.org/Archives/boost/2007/07/124502.php for a solution.

HTH,
Stephan

_______________________________________________
Boost-users mailing list
Boost-users <at> lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users
Permalink | Reply | 1 comment |

Gmane