Re: [Oorexx-devel] Question ad DecodeConditionInfo(...)

On 19.03.2011 22:52, Rick McGuire wrote: > > Sent from my iPad > > On Mar 19, 2011, at 3:41 PM, "Rony G. Flatscher" > mailto:rony.flatsc...@wu-wien.ac.at>> > wrote: > >> Sorry, after changing the code, it just occurred to me: >> "cond.program" is a RexxStringObject and should never take on NULL a

Re: [Oorexx-devel] Question ad DecodeConditionInfo(...)

On 19.03.2011 21:49, Mark Miesfeld wrote: > > Why do you clear the condition before you you decode it? > Hmm, good question. Probably, because I assume that otherwise further interactions with the Rexx interpreter would not be possible with a pending condition. (E.g. this is the case with Java AF

Re: [Oorexx-devel] Question ad DecodeConditionInfo(...)

Sent from my iPad On Mar 19, 2011, at 3:41 PM, "Rony G. Flatscher" wrote: > Sorry, after changing the code, it just occurred to me: "cond.program" is a > RexxStringObject and should never take on NULL as Jean-Louis reports, but > should rather be Nil()? They most certainly can be null. A n

Re: [Oorexx-devel] CPL V1 License superseded

Thanks Rick On 19 March 2011 21:46, Rick McGuire wrote: > No. The cpl is just as valid as it ever was. It doesn't matter. > > Rick > > Sent from my iPad > > On Mar 19, 2011, at 5:27 PM, "Sahananda (Jon) Wolfers" < > sahana...@windhorse.biz> wrote: > > Hi All, > > I don't know if this matters,

Re: [Oorexx-devel] CPL V1 License superseded

No. The cpl is just as valid as it ever was. It doesn't matter. Rick Sent from my iPad On Mar 19, 2011, at 5:27 PM, "Sahananda (Jon) Wolfers" wrote: > Hi All, > > I don't know if this matters, but I notice here that the CPL license has been > superseded by the Eclipse Public License. > >

[Oorexx-devel] CPL V1 License superseded

Hi All, I don't know if this matters, but I notice herethat the CPL license has been superseded by the Eclipse Public License. Does this matter? Does it mean ooRexx will migrate? thanks, Jon

Re: [Oorexx-devel] Question ad DecodeConditionInfo(...)

Why do you clear the condition before you you decode it? Without looking at code, can't say for sure, but that seems risky. How do you know clearing the condition doesn't set program to null? On Mar 19, 2011 12:12 PM, "Rony G. Flatscher" wrote: In a bug report which relates to BSF4ooRexx Jean

[Oorexx-devel] Beta-test for new version of BSF4ooRexx ...

Hi there, at there is a new BSF4ooRexx package, which is at a beta level (needs testing on the various platforms). It should fix the problem reported by Uli Zinngrebe. Will be testing this version over this weekend and once regarde

Re: [Oorexx-devel] Question ad DecodeConditionInfo(...)

Sorry, after changing the code, it just occurred to me: "cond.program" is a RexxStringObject and should never take on NULL as Jean-Louis reports, but should rather be Nil()? Or with other words: is it possible that the RexxStringObject members in a RexxCondition structure can be NULL? ---rony O

Re: [Oorexx-devel] Question ad DecodeConditionInfo(...)

Sorry, it should read "Nil" in the text rather than "NULL". ---rony On 19.03.2011 20:12, Rony G. Flatscher wrote: > In a bug report which relates to BSF4ooRexx Jean-Louis was kind enough > to look into the issue and came up with an analysis in >

[Oorexx-devel] Question ad DecodeConditionInfo(...)

In a bug report which relates to BSF4ooRexx Jean-Louis was kind enough to look into the issue and came up with an analysis in . According to his findings, the RexxCondition member "program" was NULL in the suppli

Re: [Oorexx-devel] Converting ooRexx from C++ to Java?

Hi David, On 18.03.2011 12:58, David Griffiths wrote: > Greetings Rexx people. Has anyone ever considered converting the > ooRexx interpreter from C++ to Java or have a feel for the level of > difficulty? I'm aware of things like BSF4Rexx but was looking for a > pure Java solution. > > I've got so

[Oorexx-devel] Subtle gcc-error on Apple

Hi there, a couple of weeks ago, after changing the code of BSF4ooRexx, the Apple version started to behave erroneously. Originally, I thought that I introduced some error into the code and tried to debug this whenever I got some free time. It turns out, that there is a subtle gcc-error on Apple