[range_ex] Developer wanted!
Hi all, About half a year ago, I took on the range_ex library from Thorsten Ottosen, aiming to make it ready for review and inclusion in boost. However, a few weeks later I found myself with a 'life' (i.e. girlfriend), so there hasn't been time for any outside-of-work hacking. I feel that range_ex deserves to be completed and would love to do it myself, but time just isn't there at the moment. range_ex is mostly just a range-ification of <numeric> and <algorithm> (i.e. versions of these functions taking Ranges rather iterator pairs) and I've been using a something similar at work. It really makes good sense to have it in boost. If anyone is willing to step up to this, let me or Thorsten know. There isn't much work really (most of it is there, just fill in the gaps, make it complete and edit a bit of the documentation). There are a few advanced features that definitely are worth pursuing in the future, but I believe a first barebone release would still improve the life of many c++ hackers. :) So, let us know if you're interested. Cheers, /Marcus
On Mon, 2007-05-07 at 22:55 +0200, Marcus Lindblom wrote:
Hi all,
About half a year ago, I took on the range_ex library from Thorsten Ottosen, aiming to make it ready for review and inclusion in boost. However, a few weeks later I found myself with a 'life' (i.e. girlfriend), so there hasn't been time for any outside-of-work hacking. I feel that range_ex deserves to be completed and would love to do it myself, but time just isn't there at the moment.
range_ex is mostly just a range-ification of <numeric> and <algorithm> (i.e. versions of these functions taking Ranges rather iterator pairs) and I've been using a something similar at work. It really makes good sense to have it in boost.
If anyone is willing to step up to this, let me or Thorsten know. There isn't much work really (most of it is there, just fill in the gaps, make it complete and edit a bit of the documentation). There are a few advanced features that definitely are worth pursuing in the future, but I believe a first barebone release would still improve the life of many c++ hackers. :)
So, let us know if you're interested.
Cheers, /Marcus
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
I will do it if I am acceptable. I know a few of you on the list. I am a professional C++ developer and have 17 years professional software development experience. Occasionally I even develop something that works. I have a number of extensions in prototype form for the range algorithm that I wished to put forward at some point in the future. I have for example an optimal resizing mechanism for target containers using template meta-programming. This makes it possible to implement a transform with a container target without forcing the client of the algorithm to continually re-evaluate whether reserve then back_insert is the best implementation, for example. The optimal re-size mechanism is implemented once per container. I have an interest in developing some useful containers to supplement the std containers. I have developed prototypes and I am in the process of taking metrics to back-up my claims that they are interesting to software developers before posting an interest query to the list. I believe these libraries would benefit from careful integration. I would be glad to be of service. Neil Groves Software Developer Irrational Daffodil Ltd.
I am very interested in this project and will be happy to help out with (perhaps some small) contributions and testing.
Thanks to everyone that has answered! There seems to be some hope after all! I'll e-mail a zip with the code I got from Thorsten (I've hardly made any changes to it) along with some other useful info to you guys. Please keep discussions on the boost list so that both I and Thorsten (who knows far more about all of this than I do) can help out if necessary. To reiterate, the main need is just to finish all the for_each/transform range wrapper functions & docs. Cheers, /Marcus
Hi Neal! I am going to develop the range_ex library to complete the current proposal. Currently I am studying the proposal in detail, and the other boost developer documentation. I am currently in the process of moving from the Bahamas to England so I am unable to give this my full attention for a couple of weeks. I imagine that within six weeks I will have some code that I would like your opinion on before submitting it for the formal review process. In this way I hope to avoid utter humiliation and a public flogging! I am very interested in any suggestions or ideas that you have. Thank you in anticipation, Neil Groves -----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Neal Becker Sent: 08 May 2007 12:04 To: boost@lists.boost.org Subject: Re: [boost] [range_ex] Developer wanted! I am very interested in this project and will be happy to help out with (perhaps some small) contributions and testing. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Marcus Lindblom wrote:
If anyone is willing to step up to this, let me or Thorsten know. There isn't much work really (most of it is there, just fill in the gaps, make it complete and edit a bit of the documentation). There are a few advanced features that definitely are worth pursuing in the future, but I believe a first barebone release would still improve the life of many c++ hackers. :)
So, let us know if you're interested.
Hi, Though I'm not sure I can join your project, I too am challenging to implement the range adaptor proposal. Here is the document and code under development: http://tinyurl.com/2fkxup http://tinyurl.com/2gncpa (not boostified) I'd be happy if my work could inspire your project. Regards, -- Shunsuke Sogame
On 5/8/07, shunsuke <pstade.mb@gmail.com> wrote:
Marcus Lindblom wrote:
If anyone is willing to step up to this, let me or Thorsten know. There isn't much work really (most of it is there, just fill in the gaps, make it complete and edit a bit of the documentation). There are a few advanced features that definitely are worth pursuing in the future, but I believe a first barebone release would still improve the life of many c++ hackers. :)
So, let us know if you're interested.
Hi, Though I'm not sure I can join your project, I too am challenging to implement the range adaptor proposal. Here is the document and code under development: http://tinyurl.com/2fkxup http://tinyurl.com/2gncpa (not boostified) I'd be happy if my work could inspire your project.
Impressive!! I especially like the fact that all functions are actually polymorphic function objects. Also your compilation of algorithms is very big. I've being doing something similar on an as need basis but on a much smaller scale. Do you plan to boostify the library and submit it for review? I would kill to use it :). The only think i do not like much is the choice of names. I would have preferred 'reverse' instead of 'reversed' or 'transform' instead of 'transformed', but it is just a matter of personal preference. gpd
Giovanni Piero Deretta wrote:
Also your compilation of algorithms is very big. I've being doing something similar on an as need basis but on a much smaller scale. Do you plan to boostify the library and submit it for review? I would kill to use it :).
Though I doubt it will be submitted, there is a plan to boostify and upload it to Vault. After all, if Boost.Range officially offers the (good portable) range adaptors, my work can be a painful experience. :-)
The only think i do not like much is the choice of names. I would have preferred 'reverse' instead of 'reversed' or 'transform' instead of 'transformed', but it is just a matter of personal preference.
It depends on whether or not the range-based STL algorithms should be placed in the same namespace as the adaptors. For now, oven follows the range library proposal. Regards, -- Shunsuke Sogame
participants (5)
-
Giovanni Piero Deretta -
Marcus Lindblom -
Neal Becker -
Neil Groves -
shunsuke