[chrono] Split into Stopwatches, Chrono, Ratio and TypeTraits.ext
Hi, As requested in this ML I have splited Boost.Chrono into 4 libraries * Boost.TypeTraits.Ext: contains the C++0x common_type and add_rvalue reference traits classes and the declval utility function * Boost Ratio: contains the C++0x ratio class * Boost.Chrono: contains the C++0x chrono library + process and thread clocks * Boost.Stopwatches: time measure and reporting More information on these libraries can be found in https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.TypeT... https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Ratio https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Chron... https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Stopw... Please let me know if you prefer separated reviews for each library. Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/
On 07/09/10 19:40, vicente.botet wrote:
Hi,
As requested in this ML I have splited Boost.Chrono into 4 libraries
* Boost.TypeTraits.Ext: contains the C++0x common_type and add_rvalue reference traits classes and the declval utility function
Coudln't this be fast forwarded as type_traits new features ?
----- Original Message ----- From: "joel falcou" <joel.falcou@lri.fr> To: <boost@lists.boost.org> Sent: Tuesday, September 07, 2010 7:54 PM Subject: Re: [boost] [chrono] Split into Stopwatches, Chrono,Ratio and TypeTraits.ext
On 07/09/10 19:40, vicente.botet wrote:
Hi,
As requested in this ML I have splited Boost.Chrono into 4 libraries
* Boost.TypeTraits.Ext: contains the C++0x common_type and add_rvalue reference traits classes and the declval utility function
Coudln't this be fast forwarded as type_traits new features ?
This was my intent. What do they think the Boost.TypeTraits maintainers? Vicente
As requested in this ML I have splited Boost.Chrono into 4 libraries
* Boost.TypeTraits.Ext: contains the C++0x common_type and add_rvalue reference traits classes and the declval utility function
Coudln't this be fast forwarded as type_traits new features ?
This was my intent. What do they think the Boost.TypeTraits maintainers?
Sounds fine to me, are there patches somewhere I can look at? Looks like I missed out add_rvalue_reference when I updated type_traits to work with rvalues earlier in the year :-( John.
----- Original Message ----- From: "John Maddock" <boost.regex@virgin.net> To: <boost@lists.boost.org> Sent: Wednesday, September 08, 2010 10:23 AM Subject: Re: [boost] [chrono] Split into Stopwatches, Chrono,Ratio and TypeTraits.ext
As requested in this ML I have splited Boost.Chrono into 4 libraries
* Boost.TypeTraits.Ext: contains the C++0x common_type and add_rvalue reference traits classes and the declval utility function
Coudln't this be fast forwarded as type_traits new features ?
This was my intent. What do they think the Boost.TypeTraits maintainers?
Sounds fine to me, are there patches somewhere I can look at?
Hi, Great. I have not developed this on the trunk. The current repository is http://svn.boost.org/svn/boost/sandbox/chrono/boost/type_traits/ http://svn.boost.org/svn/boost/sandbox/chrono/libs/type_traits_ext/ Of course, the subdirectory ext should be removed once integrated. I could move this to the trunk and provide a patch if this is better for you. I don't know how you want to include this on the current documentation. Let me know if I can do something.
Looks like I missed out add_rvalue_reference when I updated type_traits to work with rvalues earlier in the year :-(
Yes, I see that there are some rvalue traits already available. declval is declared in <utility> header on the C++0x standard, but I have added it in the type_traits directory. Should I add it into the utility directory? Vicente
Sounds fine to me, are there patches somewhere I can look at?
Hi,
Great.
I have not developed this on the trunk. The current repository is
http://svn.boost.org/svn/boost/sandbox/chrono/boost/type_traits/ http://svn.boost.org/svn/boost/sandbox/chrono/libs/type_traits_ext/
Of course, the subdirectory ext should be removed once integrated. I could move this to the trunk and provide a patch if this is better for you. I don't know how you want to include this on the current documentation. >Let me know if I can do something.
I'll take a look and see what I can integrate - bare with me it may be a few days at least.
Looks like I missed out add_rvalue_reference when I updated type_traits to work with rvalues earlier in the year :-(
Yes, I see that there are some rvalue traits already available.
declval is declared in <utility> header on the C++0x standard, but I have added it in the type_traits directory. Should I add it into the utility directory?
Not sure, it's not really a type_trait, so I guess libs/utility/ might be better. John.
Sounds fine to me, are there patches somewhere I can look at?
Hi,
Great.
I have not developed this on the trunk. The current repository is
http://svn.boost.org/svn/boost/sandbox/chrono/boost/type_traits/ http://svn.boost.org/svn/boost/sandbox/chrono/libs/type_traits_ext/
FYI, add_rvalue_reference, add_lvalue_reference, common_type and declval have now all been added to Trunk (the first three to type_traits, the latter to utility). Regards, John.
On 09/07/2010 07:40 PM, vicente.botet wrote:
Hi,
As requested in this ML I have splited Boost.Chrono into 4 libraries
* Boost.TypeTraits.Ext: contains the C++0x common_type and add_rvalue reference traits classes and the declval utility function * Boost Ratio: contains the C++0x ratio class * Boost.Chrono: contains the C++0x chrono library + process and thread clocks * Boost.Stopwatches: time measure and reporting
More information on these libraries can be found in
https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.TypeT... https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Ratio https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Chron... https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Stopw...
Please let me know if you prefer separated reviews for each library.
Hi, what are the dependencies? For example, I guess it makes no sense to review Chrono unless Ratio and TypeTraits.Ext are reviewed, too (or accepted already). Regards, Roland
----- Original Message ----- From: "Roland Bock" <rbock@eudoxos.de> To: <boost@lists.boost.org> Sent: Tuesday, September 07, 2010 9:05 PM Subject: Re: [boost] [chrono] Split into Stopwatches, Chrono,Ratio and TypeTraits.ext
On 09/07/2010 07:40 PM, vicente.botet wrote:
Hi,
As requested in this ML I have splited Boost.Chrono into 4 libraries
* Boost.TypeTraits.Ext: contains the C++0x common_type and add_rvalue reference traits classes and the declval utility function * Boost Ratio: contains the C++0x ratio class * Boost.Chrono: contains the C++0x chrono library + process and thread clocks * Boost.Stopwatches: time measure and reporting
More information on these libraries can be found in
https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.TypeT... https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Ratio https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Chron... https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction#Boost.Stopw...
Please let me know if you prefer separated reviews for each library.
Hi,
what are the dependencies? For example, I guess it makes no sense to review Chrono unless Ratio and TypeTraits.Ext are reviewed, too (or accepted already).
Hi, The dependencies are: Boost.TypeTraits.Ext Boost Ratio Boost.Chrono -> TypeTraits.Ext, Ratio Boost.Stopwatches -> Boost.Chrono You are right. It make no sense to revie a library until its dependencies are accepted. Vicente
On 09/07/2010 09:53 PM, vicente.botet wrote:
Hi,
The dependencies are:
Boost.TypeTraits.Ext Boost Ratio Boost.Chrono -> TypeTraits.Ext, Ratio Boost.Stopwatches -> Boost.Chrono
You are right. It make no sense to revie a library until its dependencies are accepted.
Vicente
BTW, are there still dependencies to changes/additions to Boost.Thread?
Roland Bock wrote:
On 09/07/2010 09:53 PM, vicente.botet wrote:
Hi,
The dependencies are:
Boost.TypeTraits.Ext Boost Ratio Boost.Chrono -> TypeTraits.Ext, Ratio Boost.Stopwatches -> Boost.Chrono
You are right. It make no sense to revie a library until its dependencies are accepted.
Hmmm- what happens if a pre-requisite library isn't accepted? Does that mean that the subsequent one can't be? Or does it mean that the subsequent one can be only if it includes the pre-requisite library as an implementation detail? Does that make any sense. This has actually come up before but has never been addressed explicitly - nor satisfactorily in my opinion. Robert Ramey
Vicente
BTW, are there still dependencies to changes/additions to Boost.Thread? _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
----- Original Message ----- From: "Robert Ramey" <ramey@rrsd.com> To: <boost@lists.boost.org> Sent: Wednesday, September 08, 2010 9:24 AM Subject: Re: [boost] [chrono] Split into Stopwatches, Chrono,Ratio and TypeTraits.ext
Roland Bock wrote:
On 09/07/2010 09:53 PM, vicente.botet wrote:
Hi,
The dependencies are:
Boost.TypeTraits.Ext Boost Ratio Boost.Chrono -> TypeTraits.Ext, Ratio Boost.Stopwatches -> Boost.Chrono
You are right. It make no sense to revie a library until its dependencies are accepted.
Hmmm- what happens if a pre-requisite library isn't accepted? Does that mean that the subsequent one can't be? Or does it mean that the subsequent one can be only if it includes the pre-requisite library as an implementation detail? Does that make any sense.
The dependencies to the TypeTraits extension could be added on a detail implementation, but I think that John want them to be integrated on without review :) I don't think Ratio should be included as an implementation detail of Boost.Chrono. And the last, if Boost.Chrono is not accepted, Boost.Stopwatches could be reimplemented using other duration types, but I don't think I will have the energy to do that. Anyway, I expect that all TypeTraits.Ext, Ratio and Chrono will be accepted, as these libraries just implement what is already specified on the C++0x standard. So I don't expect any dependency problems.
This has actually come up before but has never been addressed explicitly - nor satisfactorily in my opinion.
Please be free to start a new thread to address these possible issues, if you consider it needs to be addressed in a more satisfactory way. Best, Vicente
At Tue, 7 Sep 2010 23:24:14 -0800, Robert Ramey wrote:
Roland Bock wrote:
On 09/07/2010 09:53 PM, vicente.botet wrote:
Hi,
The dependencies are:
Boost.TypeTraits.Ext Boost Ratio Boost.Chrono -> TypeTraits.Ext, Ratio Boost.Stopwatches -> Boost.Chrono
You are right. It make no sense to revie a library until its dependencies are accepted.
Hmmm- what happens if a pre-requisite library isn't accepted? Does that mean that the subsequent one can't be? Or does it mean that the subsequent one can be only if it includes the pre-requisite library as an implementation detail? Does that make any sense.
Yes, it makes sense. It's the latter. -- Dave Abrahams BoostPro Computing http://www.boostpro.com
----- Original Message ----- From: "Roland Bock" <rbock@eudoxos.de> To: <boost@lists.boost.org> Sent: Wednesday, September 08, 2010 8:00 AM Subject: Re: [boost] [chrono] Split into Stopwatches, Chrono,Ratio and TypeTraits.ext
BTW, are there still dependencies to changes/additions to Boost.Thread?
There were no dependencies to Boost.Thread, but the oposite. What I did is to adapt the Boost.Thread interface to use Boost.Chrono. I have not included the modifications I did to Boost.Thread for version 1.43 as I have not updated them for 1.44. If you are using 1.43 you can get them from the Sandbox. I could include them also on the Boost.Chrono commpressed file if you consider necessary. Best, Vicente
On 09/08/2010 12:39 PM, vicente.botet wrote:
----- Original Message ----- From: "Roland Bock"<rbock@eudoxos.de> To:<boost@lists.boost.org> Sent: Wednesday, September 08, 2010 8:00 AM Subject: Re: [boost] [chrono] Split into Stopwatches, Chrono,Ratio and TypeTraits.ext
BTW, are there still dependencies to changes/additions to Boost.Thread?
There were no dependencies to Boost.Thread, but the oposite. What I did is to adapt the Boost.Thread interface to use Boost.Chrono. I have not included the modifications I did to Boost.Thread for version 1.43 as I have not updated them for 1.44.
Ah, thanks for the clarification :-) IMO it is much better without the modifications. Since they were not part of the official boost distribution, the modifications in Boost.Thread always made me a bit nervous... Regards, Roland
participants (6)
-
David Abrahams -
joel falcou -
John Maddock -
Robert Ramey -
Roland Bock -
vicente.botet