search for: have_boost

...6 for windows but you won't notice it since it recodes 8 bit strings automatically (which is no-op on unix and macos). If you don't want to become dependent on boost, I suggest reimplementing the most important features always using 8 bit strings and then have something like this: #ifdef HAVE_BOOST namespace fs = boost::filesystem; #else // simple implementation here #endif -Jochen

...ngs >> automatically (which is no-op on unix and macos). >> >> If you don't want to become dependent on boost, I suggest reimplementing >> the most important features always using 8 bit strings and then have >> something >> like this: >> >> #ifdef HAVE_BOOST >> namespace fs = boost::filesystem; >> #else >> // simple implementation here >> #endif >> >> -Jochen > > This happens to be very close to the code I'm working on now (I assume > this post was prompted by my patches). I'll be adding unicode sup...

...t since it recodes 8 bit strings > automatically (which is no-op on unix and macos). > > If you don't want to become dependent on boost, I suggest reimplementing > the most important features always using 8 bit strings and then have > something > like this: > > #ifdef HAVE_BOOST > namespace fs = boost::filesystem; > #else > // simple implementation here > #endif > > -Jochen This happens to be very close to the code I'm working on now (I assume this post was prompted by my patches). I'll be adding unicode support to the Windows implementation, ho...

I've been doing some experiments with the Boost Graph Library (BGL) and interfacing to llvm's GraphWriter system. I'm using GBL for some custom work and needed a way to hook BGL's write_graphviz into GraphWriter to use the existing display infrastructure. To do this I added a HAVE_BOOST configure item and #ifdef'd the Boost support code in GraphWriter. Is this useful to anyone else? Is it something desireable to contribute back? This also opens a larger question about whether making use of Boost components is a reasonable thing to do. We already have some Boost type trait...

...o use ansi or > unicode on windows. > If you implement your own code with always utf-8 this may break > compatibility with windows ansi > encoding if you don't take care and why reinvent the wheel? maybe you could > even copy/paste the > boost implementation and use the #ifdef HAVE_BOOST approach. > > -Jochen The conversion only has to be written once. And while I do like the way boost::filesystem handles locale issues, the API is not suited for LLVM for the above reasons. However, if you have a better design than what I proposed, I'd love to see it. I'm not that fam...

...e on windows. > > If you implement your own code with always utf-8 this may break > > compatibility with windows ansi > > encoding if you don't take care and why reinvent the wheel? maybe > > you could even copy/paste the > > boost implementation and use the #ifdef HAVE_BOOST approach. > > > > -Jochen > > The conversion only has to be written once. And while I do like the > way boost::filesystem handles locale issues, the API is not suited for > LLVM for the above reasons. However, if you have a better design than > what I proposed, I'd l...