- Boost - lists.boost.org

[regex] regex_match algorithm strategy?
by Lorenzo Bettini 01 Aug '07

01 Aug '07

Hi I have to split a regular expression of the shape (simplified for this example) (?:\<(or)\>)|((?:[[:word:]]+)[[:blank:]]*(?=\()) the idea is to match (actually with regex_search algorithm) or as a keyword and to match function names in function invocations (or declarations); i.e., or ( should be matched as the keyword "or" and then a parenthesis, but foo ( "foo" should be matched as a function name the above expression works correctly (and I've always used that one). Now, I had to split that expression into two regular expressions (?:\<(or)\>) ((?:[[:word:]]+)[[:blank:]]*(?=\()) and try to match the above situations the same way. Thus, I'm trying to match each one and then take the one that matched first with the biggest length (and smallest prefix but this is not important now); of course I don't get the desired behavior, since in or ( "or" is matched as a function name. Thus I was wondering: which is the actual algorithm used by regex_search? Does it take into consideration other things beside the biggest length? thanks in advance Lorenzo -- Lorenzo Bettini, PhD in Computer Science, DSI, Univ. di Firenze ICQ# lbetto, 16080134 (GNU/Linux User # 158233) HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com http://www.gnu.org/software/src-highlite http://www.gnu.org/software/gengetopt http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

2 2

[Report] 0 regressions on RC_1_34_0 (2007-08-01)
by Douglas Gregor 01 Aug '07

01 Aug '07

Boost Regression test failures Report time: 2007-07-30T10:21:37Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… No failures! Yay!

1 0

development branch(es)
by Stefan Seefeld 01 Aug '07

01 Aug '07

Hi there, with the 1.34.1 release out the door, what are the plans concerning the repository and the various branches ? Where should bug fixes and other patches go ? Is the release branch going to become the new development branch, as was suggested in a mail some moons ago ? Should I wait for the subversion migration before doing anything ? What is the timeframe for the migration ? Thanks for clarifying any of the above points. Regards, Stefan -- ...ich hab' noch einen Koffer in Berlin...

10 14

Upcoming review of Time Series
by John Phillips 01 Aug '07

01 Aug '07

With all the work for the release, there haven't been many reviews for a bit. Here is everyone's chance to get back into the reviewing swing. Next Monday (7/30/07) the review begins for the Time Series library from Eric Neibler. It is available for download now, of course using http://boost-consulting.com/vault/index.php?directory=Math%20-%20Numerics and scroll to the Time Series library. It is worth noting that the library uses components not available in the 1.34 release, and so should be tested against CVS Head. This is in the README file, but can be missed if you are just fiddling around. There is also a backport file to modify the 1.34 release if prefered. The review starts next week, but the thinking is welcome any time. Thanks for your time and effort. John Phillips Review Manager

6 20

Trac users...
by Rene Rivera 01 Aug '07

01 Aug '07

In trying to get an idea of who is who in trac I created a report to list the users and names <http://svn.boost.org/trac/boost/report/16>. But alas, many have not filled in their names. It would be, oh so nice, if people filled in the name field in their settings <http://svn.boost.org/trac/boost/settings>. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

1 0

[format] Variable argument list and string assembly
by Stephan Menzel 31 Jul '07

31 Jul '07

Hi all, I'd like to create a method using some sort of variable argument list like it would be in printf style: foo(int code, const char *fmt, ...) {} ...but using boost format. Basically, the function shall compute the format string and than create a new string with the number in "code" in front of it and the result of the computed format following. It's for returning standard replies and do some stuff depending on the error code. And it must be as performant as reasonable. I only came up with something like this: void foo(int code, boost::format &fmt) { boost::format retfrmt("%d - message: "); retfrmt % code; std::cout << retfrmt.str().append(fmt.str()) << std::endl; } int main(int argc, char **argv) { reply(42, boost::format("%d test %s\n") % 23 % "Hello"); return 0; } which does what I expected: 42 - message: 23 test Hello But I don't like the usage a lot. Especially the fact that I have to write boost::format(...) when using the function. (could use a macro so that's not the killer issue) Also there seems to be a lot of unnecessary string copying involved so I wonder if this is a good way to do this. Is there any better solution to this? Thanks and greetings... Stephan

1 0

How does V2 testing work without a Jamfile.v2?
by Peter Dimov 31 Jul '07

31 Jul '07

The regression tests for Lambda seem up and running, but I see no Jamfile.v2 in libs/lambda/test. There is a Jamfile but it appears to be v1 and is apparently not being used by the testers; I've added two new tests to it and they did not appear in the table. How does v2 testing work? Magic? Local v2 patches not reflected in HEAD even though HEAD is being tested?

3 4

[Report] 0 regressions on RC_1_34_0 (2007-07-30)
by Douglas Gregor 31 Jul '07

31 Jul '07

Boost Regression test failures Report time: 2007-07-29T16:11:56Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… No failures! Yay!

3 2

[Report] 0 regressions on RC_1_34_0 (2007-07-31)
by Douglas Gregor 31 Jul '07

31 Jul '07

Boost Regression test failures Report time: 2007-07-30T10:21:37Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… No failures! Yay!

1 0

Which Boost libraries support which compilers/versions
by Edward Diener 31 Jul '07

31 Jul '07

Let us say that a Boost user wants to find out if Boost library, for the latest Boost version, supports a particular compiler/version which he is using. He goes to the main Boost page in his HTML documenation for Boost and looks to find this information. It is reasonable to assume he looks under the Documentation link, although I personally think that a specific link, with an explanation about the information for which he is looking, on the main page should direct him to such information since it is of primary importance to Boost end users to know this. In the documentation page there is nothing on top which immediately tells him this information. When he scrolls down he sees the line which says, "See Compiler Status page to find out what library works with which compiler." So he clicks on this link. A very nice page of explanation, among its excellently written information, directs him to the Compiler Status Summary, and he clicks on this link. On the compiler status summary page he is met with links for a Developer Report, User Report, Inspection Report, and License Report and a general summary of compiler pass/fail rates on the Linux platform, which is dated 17 months ago. This is pretty poor, not only becaause it implies that Boost only support Linux compilers and the general report is from 17 months ago, but also because he has no idea what each of the links means. But let us suppose that he is undaunted and decides to click on the User Report, since he is an end user. The user report regression page is now shown and he clicks on one of the links in the list to his left to see the regression tests for that library. Let us suppose it is Boost smartptr, but it could be any library. He now looks for the compiler he is interested in among the header groupings. For the current release, on Windows, he sees Borland 5.8.2, Borland 5.9.0, msvc 8.0, intel-win 9.1, msvc 7.1, cw 9.4, intel vc 7.1 win 9.1, and msvc 8.0 wm5. He then assumes, quite reasonably, that if a specific compiler is not on this list, it is not supported in the latest release for the particular library. So evidently VC 6.0, VC 7.0, various forms of gcc, and the latest release of Comeau are not supported by any libraries for the latest release. But wait, he noticed on the Boost main page that gcc 3.4.x, vc 6.0 ( and 6.5, ie SP5 ), and vc 7.0 are supported for the latest release. So he assumes that regression tests have not been run for these compilers on Windows. Let us suppose by some quirk of fate, and the contingencies of his job, he actually has to work with on of these compilers. He now goes to the documentation for the library he is interested in, let us say smartptr again, by going back to the general Boost documentation page and clicks on smartptr. There is nothing there, as he suspects, that is going to list what compilers are supported by this library in the current release. This will generally be true for any Boost library, so I am not picking on smartptr. Now he does not know, other than by trying to actually use a Boost library, whether that library actually works with the compiler he is actually using. Finally, let us suppose by an equal quirk of fate and the contingencies of his job, that he is not using the latest release of Boost but must use an earlier release. Here the documentation for the earlier release contains no regression reports at all for that release but only for the latest release. So for any other release it is impossible to determine whether a particular compiler/version is supported by a particular library. I do realize that the config system in Boost will often tell the end user whether his compiler/version is supported in general for a particular Boost release when he tries to use it. But it does not tell the end user, in the case that the compiler/version is generally supported by the config system, whether or not a particular library supports his compiler/version and, if he can not find the results in the regression tests or in the particular library's version, it becomes difficult for him to determine. I do not think that the situation I have outlined here is good for Boost from the end users perspective. The typical end user, when wanting to use a particular 3rd party library whether of Boost or otherwise, wants to know immediately, before any other action is taken, whether that library supports the compiler/version he is using. I believe Boost should make it both much easier and always possible to determine whether a particular compiler/version can be used with a particular library in a particular version of Boost without the end user trying to use a library and, if he can not, encountering compiler errors. He may not know, even from compiler errors, whether or not the errors are his own or simply because the compiler is not supported for that library. This is not a criticism of Boost in general and certainly not the excellent smartptr library, but instead it is an effort to get Boost to create some easier system by which end users can determine whether or not they can use a Boost library in the particular working situation in which they find themselves.

7 22