[omniORB] OmniORBpy & TypeDefs

[Stefan Seefeld]

jiwils - Jimmy Wilson wrote:
> 
> Why does the idl compiler generate unusable python classes when the typedefs
> are used in the IDL?  I would like to use the typedefs instead of the names
> in the cases below, but I can't.  Could someone explain why using ELEMENT
> and Elements below would create a problem?  Since a sequence will become a
> tuple or list, I can see that the name Elements is really for ease of use,
> but what about the typedef for the structure?
> 
> // Structure for element values.
> typedef struct element_struct
> {
>         string  strName;
>         string  strValue;
> } ELEMENT;

what is the difference of this declaration compared to one without the typedef ?
I'v seen this kind of declaration in C source code but always thought it was a
C idiosyncrasy, i.e. bound to the semantics of the C language.
I never found any use for it in C++ anyways...

Regards,	Stefan
_______________________________________________________              
              
Stefan Seefeld
Departement de Physique
Universite de Montreal
email: seefelds@magellan.umontreal.ca

_______________________________________________________

      ...ich hab' noch einen Koffer in Berlin...