[Oorexx-devel] Mark Hessling's utilities and 4.0

2009-05-24 Thread Sahananda (Jon) Wolfers
I know from my tests that RexxSQL seems to work under 4.0. I have not tested it thoroughly, but I have seen it write and bring back data for a locally hosted mySQL database. I also know from talking to Mark that he can't compile his utilities for 4.0 I see from bug 2794834

Re: [Oorexx-devel] Mark Hessling's utilities and 4.0

2009-05-24 Thread Sahananda (Jon) Wolfers
Hi Rick, thanks for the explanantion. Sadly the details went right over my head, but I think I understand the gyst of it. I don't think Mark has declared that he will not support it, though that might be the case. I beleive he is travelling at the moment and may not have had a chance to

[Oorexx-devel] Before my first commit, some questions...

2009-05-24 Thread Jean-Louis Faucher
Hello I will try to commit my first fix : it's for SysSearchPath (windows platform). Before that, I have some questions : - Can I commit in the same revision the fix for v4.0beta and trunk ? according to what I see in the logs, It seems you commit separately. - I will open a bug, but I don't know

[Oorexx-devel] Problem with SysStemSort, but ...

2009-05-24 Thread Rony G. Flatscher
Got an exception with applying SysStemSort(), the debugger pointing to RexxLocalVariables.hpp, inline function: inline RexxVariable *get(size_t index) { return locals[index]; } with index=0. Unfortunately, I am not able to create an isolated test case. If I write the stem's values into a

Re: [Oorexx-devel] Problem with SysStemSort, but ...

2009-05-24 Thread Rick McGuire
Definitely not enough to determine the problem. This very much looks like there had to have been an memory overlay based on the location of the trap. The most likely explanation is a wild store by some other external routine, perhaps a problem in BSFRexx itself. Rick On Sun, May 24, 2009 at

Re: [Oorexx-devel] Problem with SysStemSort, but ...

2009-05-24 Thread Rick McGuire
Rony, I just thought of one more thing that could cause the error you're seeing. If you do an AttachThread() at some point and neglect to do a corresponding DetachThread() before returning to your caller, you'll end up with a corrupted activaation stack that will result in problems with legacy