Well, I see that the problem does come from using RexxCreateInterpreter()
instead of RexxStart().
And I don't see a quick easy solution.
--
Mark Miesfeld
On Sat, Mar 17, 2012 at 2:34 PM, Mark Miesfeld <[email protected]> wrote:
> Hi Rick,
>
> (I was going to open a bug so you could look at this later, but then
> towards the end, I realized what might be the problem, so I just took the
> bug text and pasted it in here.)
>
> Can you take a look at this when you're back home and have some time.
> Raised conditions are no longer being printed to the console. Take a
> simple example:
>
> say 'in Rexx'
> rock~put()
>
> Normally you would expect:
>
> C:\work.ooRexx>qt.rex
> in Rexx
> 4 *-* rock~put()
> Error 97 running C:\work.ooRexx\qt.rex line 4: Object method not fo
> und
> Error 97.1: Object "ROCK" does not understand message "PUT"
>
> But in trunk you get:
>
> C:\work.ooRexx>qt.rex
> in Rexx
>
> C:\work.ooRexx>
>
> I looked at it in the debugger and I can see the condition object getting
> filled in with all the correct information. And in a more complex example
> I can see the condition being propagated up. But nothing prints.
> While writing this, I realized - is this a result of using
> RexxCreateInterpreter() instead of RexxStart()? Probably.
>
> Is there an easy way to get the normal error messages printed to the
> console?
>
> --
> Mark Miesfeld
>
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
