Ok, I've got them all fixed. These were all problems in the test cases. 3 of the tests were setting shvvaluelen to the length of the value assigned to the value. Unfortunately, you were using a null string, which meant the length was 0. The native code then allocated a buffer of shvvaluelen + 1, which was too small for the value.
The 3rd case was the one with the invalid name. The variable pool interface works like variables do in the Rexx language. If you use a name like "2TEST" as a variable name for an assignment, you get an error. If you just use it as a value, it works just fine. Rick On Thu, Oct 9, 2008 at 4:23 PM, David Ashley <[EMAIL PROTECTED]> wrote: > Rick - > > Please take a look at the results of these tests. I can not tell if > these are all bugs or not. I think some of them are but others I am not > sure about. They are all RXSHV_FETCH function tests. > > Thanks, > David Ashley > > > ------------------------------------------------------------------------- > 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
