1 Jul 02:53
Re: [convert] Now with Boost.Parameter interface.
David Abrahams <dave <at> boostpro.com>
2009-07-01 00:53:41 GMT
2009-07-01 00:53:41 GMT
on Mon Jun 29 2009, "Stewart, Robert" <Robert.Stewart-AT-sig.com> wrote: >> 3. I only managed to figure out how to supply only one >> Boost.Parameter at a time like >> >> int i = convert<int>::from(str, 0)(locale_ = new_locale)(throw_ = true); >> >> I understand how to achieve >> >> int i = convert<int>::from(str, 0)((locale_ = new_locale, throw_ = true)); >> >> (with double quotes) but do not want to go there as it looks somewhat >> unorthodox. I cannot figure out how to achieve the following > > The doubled parentheses are, indeed, rare outside Boost.Preprocessor type code. > >> int i = convert<int>::from(str, 0)(locale_ = new_locale, throw_ = true); > > That is certainly preferable syntax. It's not hard to achieve, but I don't think you'd like the effect: convert<int>::from(str, 0) would have to return a function object rather than an int. What's wrong with int i = convert<int>::from(str, 0, locale_ = new_locale, throw_ = true);(Continue reading)
).
We got an internal tool here we've been ummming and ahhhing about open
sourcing. We call it "bofh" as it started as a "bunch of file
headers" but does cpps now too to keep is compiling fast. The idea
was that we do a lot of computation in R because it is convenient and
but some of our data sets are many terabytes and, thus, as some of our
stats in R were tediously slow, we wanted to make C++, our favourite
religion, like a scripting language. So we did a python shell that
feels like R but compiles with gcc/ccache/distcc in the back ground,
integrates gnuplot. We've been striving to keep the hit enter,
compile and link cycle, do useful stuff _and_ put it on the screen, to
less than a second to keep it comfortable. Write C++ on the command
RSS Feed