- Boost-users - lists.boost.org

High memory requirement of adjacency_list
by Pratyush 13 Apr '06

13 Apr '06

Hi, It seems that adjacency list takes up lot of memory than what I was expecting. Below is the code that I used for testing. int main() { typedef boost::adjacency_list<> graph_t; graph_t g(6045064); } The graph populated is taking about 190MB of memory, i.e., 32 bytes/vertex approx. I was expecting it to take 4 bytes/vertex. Am I doing something wrong? My intent is to use "vec_adj_list_impl" having no properties at all. Thanks & regards, Pratyush

5 8

Release Candiate Download Location?
by Olaf van der Spek 13 Apr '06

13 Apr '06

Hi, What is the location where the current release candidate can be downloaded?

1 0

[format] %d, %u etc. with (unsigned) char types
by Luke Elliott 13 Apr '06

13 Apr '06

I couldn't find anything on this in the list archives or the format docs, but it seems likely to have been asked before so apologies if that is the case. I would expect something like: boost::format fmt("%d"); fmt % char(0); std::cout << fmt; to output "0" given that %d is explicitly specified. This isn't the case (with VC++ 7.1 and GCC 3.4 at least, and presumably all others given this is normal stream behaviour). Obviously it can be worked around by casting to a non-char type, but that seems a shame given the nature of the library and not having to worry about type-safety too much. So, is this by design or accident? If not by design, would it be possible to change the behaviour (specialisation somewhere for (unsigned) char types or something??)? Thanks in advance Luke Elliott.

1 0

Validating file names using regex
by Jean-Sebastien Vachon 13 Apr '06

13 Apr '06

Hi there, I am sure what I am looking for exist somewhere but I haven't been able to find anything that works in boost::regex. What I am looking for is a regular expression that will validate a filename according to the specification of the OS (UNIX systems and Windows). I would be very grateful if someone could provide me with these two expressions (one for Linux and one for Windows). Later,

4 7

[xpressive] Installation prepares .lib files?
by Lynn Allan 13 Apr '06

13 Apr '06

WinXp-SP2 vc7.1 Would it be feasible/advantageous for xpressive to have an installation procedure a'la regex to build a whole series of .lib libraries? That seems to speed up builds quite a bit.

2 1

Iostreams and Tarballs?
by Gareth Foster 13 Apr '06

13 Apr '06

Hello list, I am wanting to manage a file format used by another application in my own application. They have a tar.gz file, renamed to something else. In it, there is an XML file and some .wav sound files. Can I use Boost to handle this? I would want to parse the XML from the archive, and then load a few of the sound files. What I don't want to do is something cheesy like call the tar program from mine! That's'orrible :) Cheers for any help, and code (pseudo or otherwise) would be great. Or just a yes or no you can/can't do that would be a start. Cheers all, Gaz

3 2

[review] promotion traits - result
by Tobias Schwinger 12 Apr '06

12 Apr '06

Dear Boost community, Alexander Nasonov's Promotion Traits have been accepted conditionally into Boost with 4/4 positive votes. The conditions are - an example must be added to the documentation (plus accompanying source code for the example folder), - the reference should be clarified (cv-qualification, bit fields) - further conditions might arise from the merger with the extended library (TypeTraits) and are subject to synchronization with the library maintainer (John Maddock). Thanks to Alexander for the submission and to our reviewers for their work! Regards, Tobias (Review Manager)

1 0

[multi_index] multi index container with Managed C++
by Parag Gadkari 12 Apr '06

12 Apr '06

I am having trouble while using multi index container with the "managed c++" component. Here is the typedef that the compiler won't accept. typedef multi_index_container< gcroot<interface_entity*>, indexed_by< ordered_unique<identity<gcroot<interface_entity*> > >, ordered_non_unique<member<gcroot<interface_entity*>, int,&interface_entity::entity_drawingid> >, > > entity_collection; The real deal is with the member template which needs the address of member variable of the interface_entity class. Entity class is an abstract Managed type (specified with __gc), and it is not allowed to take the address of a non-static member of a managed type. Does anybody know of a workaround? Thanks Parag

2 3

Re: [Boost-users] Validating file names using regex
by Nat Goodspeed 12 Apr '06

12 Apr '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Jean-Sebastien Vachon > Sent: Wednesday, April 12, 2006 3:38 PM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] Validating file names using regex > > I am sure what I am looking for exist somewhere but I haven't > been able to find anything that works in boost::regex. > > What I am looking for is a regular expression that will validate > a filename according to the specification of the OS (UNIX systems > and Windows). > > I would be very grateful if someone could provide me with > these two expressions (one for Linux and one for Windows). [Nat] This isn't what you're asking for -- but would it work to instantiate a boost::filesystem::path with the putative pathname in question and an appropriate checker?

2 1

[xpression] fuzzy on smatch fields
by Lynn Allan 12 Apr '06

12 Apr '06

<alert comment="xpression newbie"> Xpressive looks very promising to be able to do some things I'm trying to implement. Thanks for providing and supporting it. I was trying to figure out the fields that make up xpression smatch'es, and expanded the Example-1 to be more verbose. Basically, I tried to "unpack" as much info as I could find in the variable "what" to clarify some fuzziness on my part. There were some questions: * The suffix and prefix info seemed blank. Are there accessors to get more info to conform to my (possibly flawed) understanding of the docs? * The return from regex_id seemed to be an address (like 00323F58). Is that intended? Is there some accessor to get something more meaningful? (but I'm not clear what would be meaningful). What is the purpose of "regex_id" to the user of xpressive? * With vc7.1, there were warnings unless I cast the lengths and positions ... is this intended? void example1_verbose() { std::string hello( "hello world!" ); sregex rex = sregex::compile( "(\\w+) (\\w+)!" ); smatch what; if( regex_match( hello, what, rex ) ) { std::cout << "Overall Size: " << static_cast<int>(what.size()) << '\n'; std::cout << "Regex Id: " << what.regex_id() << '\n'; std::cout << "what[0]: " << what[0] << '\n'; std::cout << "Length(0): " << static_cast<int>(what.length(0)) << '\n'; std::cout << "Position(0): " << static_cast<int>(what.position(0)) << '\n'; std::cout << "Str(0): " << what.str(0) << '\n'; std::cout << "what[1]: " << what[1] << '\n'; std::cout << "Length(1): " << static_cast<int>(what.length(1)) << '\n'; std::cout << "Position(1): " << static_cast<int>(what.position(1)) << '\n'; std::cout << "Str(1): " << what.str(1) << '\n'; std::cout << "what[2]: " << what[2] << '\n'; std::cout << "Length(2): " << static_cast<int>(what.length(2)) << '\n'; std::cout << "Position(2): " << static_cast<int>(what.position(2)) << '\n'; std::cout << "Str(2): " << what.str(2) << '\n'; std::cout << "Prefix(): " << what.prefix() << '\n'; std::cout << "Prefix().matched: " << what.prefix().matched << '\n'; std::cout << "Prefix().length(): " << static_cast<int>(what.prefix().length()) << '\n'; std::cout << "Prefix().str(): " << what.prefix().str() << '\n'; std::cout << "Suffix(): " << what.suffix() << '\n'; std::cout << "Suffix().matched: " << what.suffix().matched << '\n'; std::cout << "Suffix().length(): " << static_cast<int>(what.suffix().length()) << '\n'; std::cout << "Suffix().str(): " << what.suffix().str() << '\n'; } } Example 1: Verbose: Overall Size: 3 Regex Id: 00323F58 what[0]: hello world! Length(0): 12 Position(0): 0 Str(0): hello world! what[1]: hello Length(1): 5 Position(1): 0 Str(1): hello what[2]: world Length(2): 5 Position(2): 6 Str(2): world Prefix(): Prefix().matched: 0 Prefix().length(): 0 Prefix().str(): Suffix(): Suffix().matched: 0 Suffix().length(): 0 Suffix().str(): </alert>

2 5