Do You realise that You are being rude without any reason ???
E
> On 1 Mar 2019, at 13:09, Rick McGuire wrote:
>
> and you should probably have already contributed those corrections rather
> than just sitting on the information
___
Oorexx-devel mai
> Those are all useful corrections, and you should probably have already
> contributed those corrections rather than just sitting on the information.
I am not "sitting on it" for fun. Everytime I started to integrate them I got
stuck on something and asked a question to this list, that in its tu
On Fri, Mar 1, 2019 at 7:05 AM P.O. Jonsson wrote:
>
> Am 01.03.2019 um 12:13 schrieb Rick McGuire :
>
> I'm not even sure why you are spending time doing this, but yes, it seems
> reasonable to only test on the things you depend on.
>
>
> One reason I am doing this is that the samples folder nee
> Am 01.03.2019 um 12:13 schrieb Rick McGuire :
>
> I'm not even sure why you are spending time doing this, but yes, it seems
> reasonable to only test on the things you depend on.
One reason I am doing this is that the samples folder needs some cleaning up
before ooRexx 5.0.0 can become a re
Test cases for the new features were a show stopper, we never asked for
tests for samples. And there are a lot of areas where we have little or no
test coverage at all that would be better addressed.
Rick
On Fri, Mar 1, 2019 at 6:23 AM P.O. Jonsson wrote:
> I got the impression test cases for t
I got the impression test cases for the samples was a „Showstopper“ for ooRexx
5.0.0 release candidate so I set out to write test cases for (almost) all of
them already in november last year; they have been laying around since then.
I’ll water the tests down then.
Hälsningar/Regards/Grüsse,
P.O
I'm not even sure why you are spending time doing this, but yes, it seems
reasonable to only test on the things you depend on.
Rick
On Fri, Mar 1, 2019 at 6:02 AM P.O. Jonsson wrote:
> Dear Developers,
>
> When checking the testcases for the samples I have the problem (on several
> samples) tha
Dear Developers,
When checking the testcases for the samples I have the problem (on several
samples) that the output is asynchronous, i.e. the output is not exactly the
same every time. One example: ccreply.rex provides this output:
rexx ccreply
Repeating "Object 1 running", 10 times.
Object 1
