-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On 08/03/2010 05:05 AM, Bjørn Roald wrote:
On 08/02/2010 07:58 PM, Johnny Willemsen wrote:
I am aware of this mapping for DDS, it is a first step in a direction, but very focused on just DDS. I have asked the DDS vendors if they want to go a step further and make a full new IDL to C++ mapping, but they don't want to do that effort.
I would hope all would somehow agree that commonality over the shared part of the IDL is worth aiming for. The problem I guess is that the DDS vendors does not have time to wait.
In TAO we have recently added some prototype support to use a std::vector for a CORBA sequence. We want to really make a new mapping,
It is unclear to me if you indicate that you tried the proposed DDS solutions and found them too be less than you desire, or that you tried them and realized that it is the way too go for CORBA as well?
The DDS mapping goes directly from the DDS PIM to the C++ PSM without IDL in between. It is really not an IDL to C++ mapping in terms of what we need for CORBA.
If part of your rationale is that CORBA need, or may need, a different mapping than the new DDS mapping for the shared parts. Could you please share this rationale.
DDS doesn't really have an IDL to C++ mapping, but directly a mapping from the DDS PIM to the C++ PSM. They are only focusing on the few interfaces DDS has, and these are all local calls, no remote calls like CORBA. The idea to use std::string and std::vector are things to reuse, but I think we need a different mapping, from IDL to C++0x Johnny -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJMYQ/FAAoJEF6eObUNSFTQpBkH/30im19lBOq0Iqx1FN1BHcqZ EBZ/o3zz7fTS7UR5Vpm+x68rhI7lyIkQtnoX4y4XL9yqnYaNp4UsvdsPAiKycEj4 dy74OHfyHg2t34B9JqFswvVKOuYVRl+euKOFNl++LJtqSL4WmOD+Ay3fK0EUfgvd Ll8xOhNTzwAhRWXCVSUtSHNQPX1/SsF1iw7PIj7g7YumXCSfZNgWqv2LGokPWbjN 09RByd425YyBYzo/PMKu8W8crQJx4Ax03AOJDbsWz3WeGbCfxIVamcvFIglUwW72 BTS7/yOA5U36Xq/hH3+w+UgOU4dQdi0QYeq1aA7dJPHJUO7r8y9G0Bh23I+9YE4= =4ihJ -----END PGP SIGNATURE-----