On 03.07.2014 16:33, Rick McGuire wrote:
> And that's why I refuse to investigate problems reported on the mailing list
> until a bug report is
> opened with an example showing what is going wrong. Investigating this
> without that would have
> been a complete waste of my time.
This works both ways.
As the infrastructure to recreate the error was rather complex, I would have
had to recreate the
BSF4ooRexx package (a Java class needed support for RexxProxy to be added),
then unbundle it and
come up with a distribution in form of an archive that allows one to simply
unzip it and setup one's
environment to run the testcase in a minimum amount of time and effort.
Rather than setting this all up and then to learn that my assumptions were
wrong, I tried to state
what I am seeing upfront to learn whether my assumptions would be correct.
Clearly, there was no
intent here that you debug such a prose.
After reading your answer I knew my assumptions about the package behaviour
were correct and started
out to create a testcase. In the process I came up with the idea to do it in
pure Rexx as this was
possible in this case. As another result I would become able to find my own
error which I reported.
---rony
P.S.: Currently, I have only intermittent and short time slots available to
turn back to programming
and testing. Hence, I overlooked the name of my test script to be test.rex
which gets invoked if no
routine by the name of test was found, yielding the error 11. Next time, I will
upload the scripts
as attachments and not inline, to also cover such possible errors.
>
> On Thu, Jul 3, 2014 at 9:36 AM, Rony G. Flatscher <[email protected]
> <mailto:[email protected]>> wrote:
>
> Rick,
>
> On 03.07.2014 13:39, Rick McGuire wrote:
> > If you want this investigated, then you need to file the bug report
> first with a means of
> > reproducing this.
> Thank you for the offer!
>
> While trying to come up with an ooRexx-only example for this observed
> behavior, I found out that I
> committed an unnoticed error in the Rexx code: the Rexx code for the
> second routine was built in a
> string variable where each statement was ended with a semi-colon, but no
> .endofline. Right before
> the test routine directive a line-comment was used, which caused all
> following code to be part of
> the comment.
>
> Sorry for the false alarm!
>
> ---rony
>
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
