[1.48.0.beta 1][interprocess] detail namespace
Hi, is the change of the name of the namespace 'detail' to 'ipcdetail' intended to be in the release? Isn't it over-qualified as it is located in the the namespace 'boost::interproces' anyway?. Btw it breaks our code and should mentioned in the release notes of the library. Thanks for reading, Jan.
Le 28/10/11 11:12, Jan Boehme a écrit :
Hi,
is the change of the name of the namespace 'detail' to 'ipcdetail' intended to be in the release? Isn't it over-qualified as it is located in the the namespace 'boost::interproces' anyway?. Btw it breaks our code and should mentioned in the release notes of the library.
I guess that the detail namespace was not documented in the previous release. In this case the author has the freedom of changing any implementation detail. IMO, Ion has a good reason to do it. How your code is broken? Best, Vicente
On 10/28/2011 12:12 PM, Vicente J. Botet Escriba wrote:
Le 28/10/11 11:12, Jan Boehme a écrit :
Hi,
is the change of the name of the namespace 'detail' to 'ipcdetail' intended to be in the release? Isn't it over-qualified as it is located in the the namespace 'boost::interproces' anyway?. Btw it breaks our code and should mentioned in the release notes of the library.
I guess that the detail namespace was not documented in the previous release. In this case the author has the freedom of changing any implementation detail. IMO, Ion has a good reason to do it.
I'd bet.
How your code is broken?
It's nothing dramatic. It's caused by the new name of this namespace and the usage of some members of it in an extension. I wanted to have it confirmed to make sure our adaptions can remain after an official 1.48 release. Our code must support various Boost version so we solved it using the pre-processor.
Best, Vicente
Cheers, Jan.
On 10/28/2011 02:11 PM, Philippe Vaucher wrote:
How your code is broken?
It's nothing dramatic. It's caused by the new name of this namespace and the usage of some members of it in an extension.
I think the real question is why did you use the detail:: namespace at all.
However it's not my question. I use it 'cause I have to and it's more than likely that you have to if you develop an extension to interprocess.
It's supposed to be implementation details.
Clear. I just wondered about the name and wanted to verify. No big deal.
Philippe
Jan
Le 28/10/11 13:27, Jan Boehme a écrit :
On 10/28/2011 12:12 PM, Vicente J. Botet Escriba wrote:
Le 28/10/11 11:12, Jan Boehme a écrit :
Hi,
is the change of the name of the namespace 'detail' to 'ipcdetail' intended to be in the release? Isn't it over-qualified as it is located in the the namespace 'boost::interproces' anyway?. Btw it breaks our code and should mentioned in the release notes of the library.
I guess that the detail namespace was not documented in the previous release. In this case the author has the freedom of changing any implementation detail. IMO, Ion has a good reason to do it. I'd bet.
How your code is broken? It's nothing dramatic. It's caused by the new name of this namespace and the usage of some members of it in an extension. I wanted to have it confirmed to make sure our adaptions can remain after an official 1.48 release. Our code must support various Boost version so we solved it using the pre-processor.
OK. I understand your concern. Best, Vicente
El 28/10/2011 11:12, Jan Boehme escribió:
Hi,
is the change of the name of the namespace 'detail' to 'ipcdetail' intended to be in the release? Isn't it over-qualified as it is located in the the namespace 'boost::interproces' anyway?. Btw it breaks our code and should mentioned in the release notes of the library.
Well, "detail" is "implementation detail", no one should depend on this, it is not a public interface. And I changed because there were many problems in some compilers with function resolution ambiguities, as same function/class names were in boost:: in boost::interprocess or boost::intrusive. What are you using from that namespace? Best, Ion
participants (4)
-
Ion Gaztañaga -
Jan Boehme -
Philippe Vaucher -
Vicente J. Botet Escriba