Re: [ccmtools-devel] extended IDL?

[Egon T. <ego...@ut...>]

Hey Darrell!

Darrell Schiebel wrote:
> The python version of the test/tutorial is below. I set it up so that 
> the component homes are automatically created, but in thinking about 
> it, I think perhaps the user should start with the home-finder. This 
> would allow (at some point) remote and local components to be mixed 
> easier. Do you agree?

Yes, I do!

>> Currently, we are planning to use the IDL any mechanism to pass  dynamic
>> data structures as method parameters. In that case we have to options:
>>
>> a) We define a default mapping from IDL any to dynamic C++ structures
>> (here we can use the WX::Utils::value* classes provided by the
>> cpp-environment).
>>
>> b) We allow the developer to define its own set of IDL any to C++
>> converter which can be hooked in at generation time (e.g. an XML file
>> contains the converter signatures which can be used by the ccmtools
>> generators).
>>
>> IDL any does not support type checking at compile time, but with an
>> appropriate mapping to C++ we do not have to pay the XML parsing
>> overhead in the local case - we can pass C++ references to dynamic C++
>> structures.
> 
> 
> The "any" with generated to/from mappings in the generated code makes  a
> lot of sense, thanks Egon. We'll probably do that to transport 
> heterogeneous dictionaries as well as multi-dimensional arrays.  Before
> too long I'll have to create RPMs so that others can use my  python
> generator. At that point, I'll send you a copy and try to help  clean up
> any unnecessary deviation from the current state of the CVS  repository.

Thanks a lot.
I'm happy to see these pretty interesting extensions to ccmtools. Is
there a way to get a deeper insight to your work? Maybe we can discuss
some details on ccmtools-devel...

:-) Egon

PS: Are you interested in becoming an official member of the ccmtools
developer community?