No, not true. Just a simple case to a (void *) is sufficient. See the equivalent code in the rexxutil SysDumpVariables code. I'm not sure I want to give up the advantages that are gained from making that a const value.
Rick On Wed, Oct 8, 2008 at 2:25 PM, David Ashley <[EMAIL PROTECTED]> wrote: > Rick - > > Before I fixed this I wanted to run this by you to see if you had ideas > on a work around. > > Currently the SHVBLOCK defines the shvname RXSYTING struct as a const. > This is fine for all operations except RXSHV_NEXTV. In this case ooRexx > can allocate the memory for shvname.strptr. The problem is that the > memory can not be freed because it is defined as const. The only fix for > this is to remove the const attribute for the shvname struct. > > Do you agree with my analysis or do you have a suggestion for a work around? > > David Ashley > ooRexx Team > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
