RE: ORBit_small_freekids howto
- From: "Johan Antonsson" <Johan Antonsson ibitec se>
- To: "Michael Meeks" <michael ximian com>
- Cc: "Frank Rehberger" <Frank Rehberger web de>,"Orbit-List (E-mail)" <orbit-list gnome org>
- Subject: RE: ORBit_small_freekids howto
- Date: Mon, 12 Jan 2004 13:45:31 +0100
Hi Michael,
I'm still confused over which operations I should use when allocating and freeing structs, etc generated from IDL. I don't want to use the internal operations if not necessary, I wanna use the recommended appoach. Apparently I should always use CORBA_free() when freeing CORBA-stuff right?, but is there a corresponding alloc operation or am I supposed to use the generated macros such as se_foi_flex_appl_adapterinterface_dc_C_KeyValuePair__alloc()? I'm a CORBA/Orbit newbie so I appreciate if you could be extra clear when explaining this stuff to me ;-). Maybe I'll learn enough to write the gtk-doc comments, but I'm not there yet :-).
Is it worthwhile to have a look at the Gnome implementation to find out how to use more advanced aspects of Orbit2? Any hints on where to look?
Thanks for your help
Regards
/Johan
-----Original Message-----
From: Michael Meeks [mailto:michael@ximian.com]
Sent: den 12 januari 2004 11:53
To: Johan Antonsson
Cc: Frank Rehberger; Orbit-List (E-mail)
Subject: RE: ORBit_small_freekids howto
Hi Johan,
On Fri, 2004-01-09 at 15:43, Johan Antonsson wrote:
> Does this mean that I'm not supposed to use the macros generated
> from idl and which are located in the .h file? Se below. I was
> under the assumption that I have to allocate an
> se_foi_flex_appl_adapterinterface_dc_C_KeyValuePair with
> se_foi_flex_appl_adapterinterface_dc_C_KeyValuePair__alloc().
> If that's not the case, what is the recommended approach?
> ORBit_alloc_tcval, malloc? Do you have any good examples
> of similar use?
I think the trick is: if you want to use these internals - be clueful;
ie. go read the implementation - which is not complex to see what it
does; write a gtk-doc style comment and send it as a patch to us :-)
Otherwise - just use the generated headers.
The reason this is a macro is to save time / space / link slots. It
frees the allocated children of a complex type but not the type itself.
HTH,
Michael.
--
michael@ximian.com <><, Pseudo Engineer, itinerant idiot
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]