Re: Need new ORBit

[bob thestuff net]

Well, in the generated code, it has something like this:
      environment__free(&env, NULL, CORBA_FALSE);

As you can see, it is hardcoded to not free the strings.
But if you look in environment__free:
gpointer 
environment__free(gpointer mem, gpointer dat, CORBA_boolean
free_strings)
{
   blade_environment *var = mem;
<snip>
   if (free_strings) {
      CORBA_string__free(&(var->user), NULL, free_strings);
   }   if (free_strings) {
      CORBA_string__free(&(var->session_key), NULL, free_strings);
   }
<snip>
   return (gpointer) (var + 1);
}

It has code to free the strings. It is generateing code that can not be
used. Why is this? Am I forced to free all my strings myself(I have a
lot)? Why cant I take advantage of code that is already there? It would
make things smaller, faster, and easier on the end coder.

On Wed, 16 Feb 2000, Elliot Lee wrote:

> On Wed, 16 Feb 2000 bob@thestuff.net wrote:
> 
> > Request. The orbit generated code is hardcoded to leak strings.
> 
> ORBit is working fine. Your code is probably broken or violating the CORBA
> memory management rules.
> 
> -- Elliot
> If imprinted foil seal under cap is broken or missing when purchased, do not use. 
> 
>