Re: [Oorexx-devel] Test suite fails on Fedora 31

[Enrico Sorichetti via Oorexx-devel]

Thank You for caring. The fix works
BUT …..
Since UNIX is case sensitive 
IMO It is just plain wrong to match the lower case of a file name

I just renamed testOORexx.rex to testoorexx.rex 
And invoking the test suite with 
rexx testOORexx . . .

It should have returned
 Failure during initialization: Program "testOORexx" was not found.
But the test suite was run anyway 

For the well known Rexx extension CLS,cls,REX,rex 
Is reasonable ( when the extension is not specified) to search for upper and 
lower case extensions
But only for the extension and not on the full filename

Cheers 
Enrico


> On 1 Apr 2020, at 11:20, Enrico Sorichetti via Oorexx-devel 
>  wrote:

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] DocBook 4.5 tagging

[Rony G. Flatscher]

Erich, thank you very much for the links!

On 01.04.2020 17:35, Erich Steinböck wrote:
> Rony, you find the DocBook reference at 
> https://tdg.docbook.org/tdg/4.5/docbook.html
> Each tag lists its allowed parents and children (if any).
>
> You can find ooRexx 4.2 documentation at
> https://sourceforge.net/projects/oorexx/files/oorexx-docs/4.2.0/
Looking at the Set or Bag classes (in the 4.2 rexxpg.pdf book [1]) it is not 
documented that they
are inheriting from the MapCollection mixin class as well (and also it is not 
possible to realize
that they are actually specializing the ooRexx Object class directly), same is 
true for all classes
that inherit from more than one mixin class, e.g. the InputOutputStream mixin 
class being shown as a
specialisation of the Object class, no information that it actually inherits in 
addition from the
mixin class InputStream and the mixin class OutputStream itself, etc.!

This is probably owed to the fact that the author tried to have each class only 
once in the class
hierarchy to make it easy comprehendable. Having and employing multiple 
inheritance, however, would
probably mandate in these cases that these classes are not only showing 
directly underneath the
subclass/mixinclass'd class, but in addition also underneath each mixin class 
that gets inherited.
This probably will cause problems for beginners or people coming from languages 
that do not employ
multiple-inheritance (why does a class appear more than once in a hierarchy?).

Hence my attempt to "escape" this problem by depicting the class hierarchy such 
that each class is
shown only once, directly under the class it subclasses/mixinclasses, but 
giving the additional
information about inheritance, if employed (and which mixin classes in which 
sequence get inherited)
via "(inherit x y)" and also which class can be used for multiple inheritance 
by supplying the
"(mixin)" information next to those classes.

If time permits, I can come up with a class tree that lists classes that employ 
multiple inheritance
underneath each mixin class they inherit in addition, just to see the 
difference and guessing
whether it is clearer for beginners and newcomers by comparison.

Also, I could come up with additional listings in the sections that describe 
each class briefly that
list in the case of mixin classes the classes that inherit directly from it. 
This way studying the
brief descriptions of the classes will make the reader aware of this as well. 
Also this brief
description of classes could get extended with the brief information like "This 
class is a
mixinclass and it can therefore be inherited by other classes." and "This class 
inherits in addition
from the following mixin classes: ...". However, I would only add that 
information if it is seen as
helpful for beginners and newcomers.

---rony

[1] rexxpg.pdf, ooRexx 4.2:





___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] DocBook 4.5 tagging

[Erich Steinböck]

Rony, you find the DocBook reference at
https://tdg.docbook.org/tdg/4.5/docbook.html
Each tag lists its allowed parents and children (if any).

You can find ooRexx 4.2 documentation at
https://sourceforge.net/projects/oorexx/files/oorexx-docs/4.2.0/
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the documentation

[P.O. Jonsson]

Hi Gil,

No objections whatsoever, I just wonder if this is the same cause as found 
while trying (failing :-( ) to find the cause earlier:

Hi Chris,
The role value 'italic' is not actually a recognized value in the 
stylesheets.  Rather, italic font-style is the default output for emphasis. 
In FO, if role is not 'strong' or 'bold', you automatically get the default 
italic.

-> Try changing  to 


Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 01.04.2020 um 17:21 schrieb Gil Barmwater :
> 
> This inspired me to do some digging into the problem now that Rony has 
> determined the cause. It appears that the  tag confuses the 
> stlyesheet which would have otherwise picked up the text. However, there are 
> other ways to specify the text, one of which is to include an "xreflable" 
> attribute. I have tried that and it allows one to keep the "emphasis" without 
> generating the error messages. I plan to make the changes shortly so the 
> original look will be preserved and the ??? will be eliminated. Any 
> objections?
> 
> Gil
> On 3/31/2020 4:48 PM, Gil Barmwater wrote:
>> Well done! I never would have thought to try that since the documentation 
>> would lead one to believe it was legal. Thanks Rony!
>> 
>> Gil
>> On 3/31/2020 2:52 PM, Rony G. Flatscher wrote:
>>> Found the cause: there are term elements which have their text embedded in 
>>> emphasis tags causing the error messages:
>>> 
>>> Don't know what gentext to create for xref to: "emphasis"
>>> Fixed them in "wineventlog.xml", ran doc2pdf.cmd and doc2html.cmd 
>>> successfully, therefore committed with [r12032].
>>> 
>>> ---rony
>>> 
>>> On 31.03.2020 17:41, Gil Barmwater wrote:
 There appears to be two issues based on the messages generated by the 
 transform step. The first - Warning: multiple "IDs" for constraint 
 linkend: - occurs 7 times for 3 different values: clsWindowObject, 
 childatpositionwo, and windowatpositionwm. These might be simple typos(?).
 
 The second - Don't know what gentext to create for xref to: "emphasis" - 
 occurs 32 times and seems to correspond with the ??? that appears 32 times 
 in the PDF generated by Publican. Finding the XML for that area seems to 
 show a "linkend=" but the value does not get substituted.
 
 The second issue seems to be confined to the WindowsEventLogClass chapter.
 
 That's as far as I have gotten. Hope it is enough to determine the fix 
 needed.
 
 Gil
 On 3/31/2020 11:20 AM, Rick McGuire wrote:
> 
> 
> On Tue, Mar 31, 2020 at 11:04 AM Gil Barmwater  > wrote:
> Well, as I mentioned, this was a problem with the PDF builds as well. So 
> I looked in the PDF.xsl for where the "No adjustColumnWidths function 
> available" message was generated and found that there was a parameter - 
> tablecolumns.extension - that controlled that function. Since we don't 
> use Perl and don't have the Perl function anyway, I decided to try 
> disabling the function by changing the parameter expecting this would 
> cause other side effects. Luckily, it didn't. So when this surfaced in 
> the HTML generation, I found the same parameter in the xhtml-common.xsl 
> file and changed it there too.
> 
> The problems with winextensions are not not related but are due to "bad" 
> Docbook code. I know where they are coming from but need to understand 
> what the author was attempting to do and then determine how to do it 
> "right".
> 
> Please explain what the issue it so we can help to decide now to fix it. 
> 
> Rick
> 
>  
> Gil
> On 3/31/2020 10:26 AM, P.O. Jonsson wrote:
>> Ok, missed that part :-(
>> 
>> I have replaced xhtml-common.xsl now and winextensions build as it 
>> should, so this was probably the problem. This tiniest change cased the 
>> problem thus:
>> 
>> 1
>> 
>> changed into
>> 
>> 0 > Gil Barmwater
>> 
>> 
>> 
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net 
>> 
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel 
>> 
> -- 
> Gil Barmwater
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Building the documentation

[Gil Barmwater]

This inspired me to do some digging into the problem now that Rony has 
determined the cause. It appears that the  tag confuses the 
stlyesheet which would have otherwise picked up the text. However, there 
are other ways to specify the text, one of which is to include an 
"xreflable" attribute. I have tried that and it allows one to keep the 
"emphasis" without generating the error messages. I plan to make the 
changes shortly so the original look will be preserved and the ??? will 
be eliminated. Any objections?


Gil

On 3/31/2020 4:48 PM, Gil Barmwater wrote:


Well done! I never would have thought to try that since the 
documentation would lead one to believe it was legal. Thanks Rony!


Gil

On 3/31/2020 2:52 PM, Rony G. Flatscher wrote:


Found the cause: there are term elements which have their text 
embedded in emphasis tags causing the error messages:


Don't know what gentext to create for xref to: "emphasis"

Fixed them in "wineventlog.xml", ran doc2pdf.cmd and doc2html.cmd 
successfully, therefore committed with [r12032].


---rony


On 31.03.2020 17:41, Gil Barmwater wrote:


There appears to be two issues based on the messages generated by 
the transform step. The first - Warning: multiple "IDs" for 
constraint linkend: - occurs 7 times for 3 different values: 
clsWindowObject, childatpositionwo, and windowatpositionwm. These 
might be simple typos(?).


The second - Don't know what gentext to create for xref to: 
"emphasis" - occurs 32 times and seems to correspond with the ??? 
that appears 32 times in the PDF generated by Publican. Finding the 
XML for that area seems to show a "linkend=" but the value does not 
get substituted.


The second issue seems to be confined to the WindowsEventLogClass 
chapter.


That's as far as I have gotten. Hope it is enough to determine the 
fix needed.


Gil

On 3/31/2020 11:20 AM, Rick McGuire wrote:



On Tue, Mar 31, 2020 at 11:04 AM Gil Barmwater 
mailto:gbarmwa...@alum.rpi.edu>> wrote:


Well, as I mentioned, this was a problem with the PDF builds as
well. So I looked in the PDF.xsl for where the "No
adjustColumnWidths function available" message was generated
and found that there was a parameter - tablecolumns.extension -
that controlled that function. Since we don't use Perl and
don't have the Perl function anyway, I decided to try disabling
the function by changing the parameter expecting this would
cause other side effects. Luckily, it didn't. So when this
surfaced in the HTML generation, I found the same parameter in
the xhtml-common.xsl file and changed it there too.

The problems with winextensions are not not related but are due
to "bad" Docbook code. I know where they are coming from but
need to understand what the author was attempting to do and
then determine how to do it "right".

Please explain what the issue it so we can help to decide now to 
fix it.


Rick

Gil

On 3/31/2020 10:26 AM, P.O. Jonsson wrote:

Ok, missed that part :-(

I have replaced xhtml-common.xsl now and winextensions build
as it should, so this was probably the problem. This tiniest
change cased the problem thus:

1

changed into

0 

Re: [Oorexx-devel] DocBook 4.5 tagging

[P.O. Jonsson]

Dear Rony,

Ad


> Am 01.04.2020 um 16:08 schrieb Rony G. Flatscher :
> 
> Also, I think it is very important to have a section about tagging the ooRexx 
> documentation with examples of how to do it and also giving don'ts that may 
> not be obvious. (This is something I have on my todo list, once the 
> documentation processes has been established and once having enough insight 
> and knowledge for doing that. My test.pdf book is a first start as it also 
> includes the original DocBook sample markup.)
> 
>> 

I suggest to bring that to a section of ooRexxBuild (Folder Buildmachine is 
internally called ooRexxBuild) book

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] DocBook 4.5 tagging

[Rony G. Flatscher]

On 01.04.2020 16:24, Gil Barmwater wrote:
>
> I have found the following links useful re. DocBook tags:
>
> https://tdg.docbook.org/tdg/4.5/docbook.html - this is a good reference for 
> tags and attributes
>
> www.sagehill.net/docbookxsl/ - more explanations on things like "chunking" or 
> "xref"; NB this is
> DocBook 5!
>
Thank you, Gil!

---rony




___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] DocBook 4.5 tagging

[Gil Barmwater]

I have found the following links useful re. DocBook tags:

https://tdg.docbook.org/tdg/4.5/docbook.html - this is a good reference 
for tags and attributes


www.sagehill.net/docbookxsl/ - more explanations on things like 
"chunking" or "xref"; NB this is DocBook 5!


Gil

On 4/1/2020 10:08 AM, Rony G. Flatscher wrote:


Hi Erich,

On 31.03.2020 23:17, Erich Steinböck wrote:

Rony, we're on Docbook 4.5.
xref's within classname (or filename) are not allowed.


hmm, good to know (was not aware of this as it had worked without any 
errors)! :)


I would appreciate if you could give some pointers where this gets 
documented. Looking through the DocBook 4.5 DTDs and modules [1] I 
could not see that exclusion, but then it may have to do with 
inferrals that I am not aware of (it has been far too long that I 
fiddled with SGML/XML DTDs).


Thank you also for the snippet at the bottom for classname examples. 
The current version had them removed already, however these instances 
could still be found:


  * classname:
provide.xml: class.

  * filename:
samples.xml:class implemented in the package .
samples.xml:Sample uses of the pipe implementation
in package . 
samples.xml:defined in package , which makes sure that

Will remove the classname and filename tags later.

You may want to check with the docs or our existing xml's before 
using any special xml tagging.


I have done that as I have explained already in another post.

The rexxpg book was almost devoid of semantic markup it just used 
emphasis at places, which I copied, short of knowing any better at 
that time. Later when learning more about the elements I replaced all 
emphasis markup with semantic markup where spotted, a *lot* of 
additional work that I could have saved, if I had known earlier, i.e. 
if it was explicitly documented someplace! Looking around the rexxpg 
book originally did not unveil how to use the available markup in a 
more correct manner.


So what you call "special xml tagging" was unintentional, short of 
knowing better.


Also, I think it is very important to have a section about tagging the 
ooRexx documentation with examples of how to do it and also giving 
don'ts that may not be obvious. (This is something I have on my todo 
list, once the documentation processes has been established and once 
having enough insight and knowledge for doing that. My test.pdf book 
is a first start as it also includes the original DocBook sample markup.)



Please revert this change.

Will do later.
Also the rexxpg modification to the class hierarchy now fails to show 
Array being an OrderedCollection which in turn being a Collection 
which is the whole idea of this diagram. Just compare with the 4.2 
version.
This "Basics of Classes" diagram should give the oo beginner an 
overview and should be as simple as possible.


Do you have a pointer to the 4.2 pdf  version for comparison?

The current hierarchy is as simple as possible using ooRexx subclasses 
and superclasses methods itself with the aim to have each class shown 
once in the diagram to make it "as simple as possible" indeed!


If you look at the Array class you immediately see that Array is not 
only a subclass of Object, but inherits the OrderableCollection 
behaviour, which via inheritance is also a Collection. This follows 
from multiple inheritance applied to this collection class. This the 
reason BTW why I added the information "(mixin)" and "(inherit x y)" 
next to the classes in the class tree: to communicate e.g. that the 
Array class is also an OrderableCollection, making it a Collection.


Adding classes that use multiple inheritance to all those mixin 
classes in the class hierarchy they inherit in addition will cause 
classes to be shown all over the place, which I fear is making the 
hierarchy "difficult" and truly confusing for beginners and newcomers 
(why is this class showing up more than one time, all over these 
places?). E.g. the classes Bag, DateTime, File, InputOutputStream,  
Message, Set and TimeSpan which actually are subclassing/inheriting a 
total of three classes each at the same time?


Maybe listing the inheriting classes in the brief description of 
Comparable, MapCollection, Orderable, etc. and at the same time 
listing the superclasses (immediate and inherited) in the brief 
description of the respective classes like for Array, Message, etc.?


---rony

[1] DocBook 4.5 XML, module and enttiy files (look for the zip-file 
for downloading): .





On Sun, Mar 29, 2020 at 8:40 PM orexx--- via Oorexx-svn 
> wrote:


Revision: 12022
http://sourceforge.net/p/oorexx/code-0/12022
Author:   orexx
Date:     2020-03-29 18:40:42 + (Sun, 29 Mar 2020)
Log Message:
---
Add missing classes, reorder, standardize id-link names, add
links from the class tree to the individual brief class descriptions.

Modified Paths:

Re: [Oorexx-devel] DocBook 4.5 tagging

[Rony G. Flatscher]

Hi Erich,

On 31.03.2020 23:17, Erich Steinböck wrote:
> Rony, we're on Docbook 4.5.
> xref's within classname (or filename) are not allowed.

hmm, good to know (was not aware of this as it had worked without any errors)! 
:)

I would appreciate if you could give some pointers where this gets documented. 
Looking through the
DocBook 4.5 DTDs and modules [1] I could not see that exclusion, but then it 
may have to do with
inferrals that I am not aware of (it has been far too long that I fiddled with 
SGML/XML DTDs).

Thank you also for the snippet at the bottom for classname examples. The 
current version had them
removed already, however these instances could still be found:

  * classname:
provide.xml: class.

  * filename:
samples.xml:class implemented in the package .
samples.xml:Sample uses of the pipe implementation in 
package . 
samples.xml:defined in package , which makes
sure that

Will remove the classname and filename tags later.

> You may want to check with the docs or our existing xml's before using any 
> special xml tagging.

I have done that as I have explained already in another post.

The rexxpg book was almost devoid of semantic markup it just used emphasis at 
places, which I
copied, short of knowing any better at that time. Later when learning more 
about the elements I
replaced all emphasis markup with semantic markup where spotted, a *lot* of 
additional work that I
could have saved, if I had known earlier, i.e. if it was explicitly documented 
someplace! Looking
around the rexxpg book originally did not unveil how to use the available 
markup in a more correct
manner.

So what you call "special xml tagging" was unintentional, short of knowing 
better.

Also, I think it is very important to have a section about tagging the ooRexx 
documentation with
examples of how to do it and also giving don'ts that may not be obvious. (This 
is something I have
on my todo list, once the documentation processes has been established and once 
having enough
insight and knowledge for doing that. My test.pdf book is a first start as it 
also includes the
original DocBook sample markup.)

> Please revert this change.
Will do later.
> Also the rexxpg modification to the class hierarchy now fails to show Array 
> being an
> OrderedCollection which in turn being a Collection which is the whole idea of 
> this diagram.  Just
> compare with the 4.2 version.
> This "Basics of Classes" diagram should give the oo beginner an overview and 
> should be as simple
> as possible.

Do you have a pointer to the 4.2 pdf  version for comparison?

The current hierarchy is as simple as possible using ooRexx subclasses and 
superclasses methods
itself with the aim to have each class shown once in the diagram to make it "as 
simple as possible"
indeed!

If you look at the Array class you immediately see that Array is not only a 
subclass of Object, but
inherits the OrderableCollection behaviour, which via inheritance is also a 
Collection. This follows
from multiple inheritance applied to this collection class. This the reason BTW 
why I added the
information "(mixin)" and "(inherit x y)" next to the classes in the class 
tree: to communicate e.g.
that the Array class is also an OrderableCollection, making it a Collection.

Adding classes that use multiple inheritance to all those mixin classes in the 
class hierarchy they
inherit in addition will cause classes to be shown all over the place, which I 
fear is making the
hierarchy "difficult" and truly confusing for beginners and newcomers (why is 
this class showing up
more than one time, all over these places?). E.g. the classes Bag, DateTime, 
File,
InputOutputStream,  Message, Set and TimeSpan which actually are 
subclassing/inheriting a total of
three classes each at the same time?

Maybe listing the inheriting classes in the brief description of Comparable, 
MapCollection,
Orderable, etc. and at the same time listing the superclasses (immediate and 
inherited) in the brief
description of the respective classes like for Array, Message, etc.?

---rony

[1] DocBook 4.5 XML, module and enttiy files (look for the zip-file for 
downloading):
.

>
>
> On Sun, Mar 29, 2020 at 8:40 PM orexx--- via Oorexx-svn 
>  > wrote:
>
> Revision: 12022
>           http://sourceforge.net/p/oorexx/code-0/12022
> Author:   orexx
> Date:     2020-03-29 18:40:42 + (Sun, 29 Mar 2020)
> Log Message:
> ---
> Add missing classes, reorder, standardize id-link names, add links from 
> the class tree to the
> individual brief class descriptions.
>
> Modified Paths:
> --
>     docs/trunk/rexxpg/en-US/provide.xml
>
> Modified: docs/trunk/rexxpg/en-US/provide.xml
> ===
> --- docs/trunk/rexxpg/en-US/provide.xml 2020-03-29 18:39:56 UTC (rev 
> 12021)
> +++ 

[Oorexx-devel] Test suite fails on Fedora 31

[Enrico Sorichetti via Oorexx-devel]

Here are the details
Enrico 


[vagrant@fedora ooRexx.testSuite.svn]$ uname -a
Linux fedora 5.5.11-200.fc31.x86_64 #1 SMP Mon Mar 23 17:32:43 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux
[vagrant@fedora ooRexx.testSuite.svn]$ 


[vagrant@fedora ooRexx.svn]$ clang --version
clang version 9.0.1 (Fedora 9.0.1-2.fc31)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
[vagrant@fedora ooRexx.svn]$ 

And … before You ask it behaves the same with gcc
[vagrant@fedora ooRexx.testSuite.svn]$ gcc --version
gcc (GCC) 9.2.1 20190827 (Red Hat 9.2.1-1)
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


[vagrant@fedora ooRexx.svn]$ svn info
Path: .
Working Copy Root Path: /home/vagrant/ooRexx.svn
URL: https://svn.code.sf.net/p/oorexx/code-0/main/trunk
Relative URL: ^/main/trunk
Repository Root: https://svn.code.sf.net/p/oorexx/code-0
Repository UUID: 0b6cbdbe-3aab-466e-b73a-abd511dda0a2
Revision: 12034
Node Kind: directory
Schedule: normal
Last Changed Author: erich_st
Last Changed Rev: 12034
Last Changed Date: 2020-03-31 22:41:17 +0200 (Tue, 31 Mar 2020)


[vagrant@fedora ooRexx.testSuite.svn]$ svn info
Path: .
Working Copy Root Path: /home/vagrant/ooRexx.testSuite.svn
URL: https://svn.code.sf.net/p/oorexx/code-0/test/trunk
Relative URL: ^/test/trunk
Repository Root: https://svn.code.sf.net/p/oorexx/code-0
Repository UUID: 0b6cbdbe-3aab-466e-b73a-abd511dda0a2
Revision: 12034
Node Kind: directory
Schedule: normal
Last Changed Author: erich_st
Last Changed Rev: 12033
Last Changed Date: 2020-03-31 22:40:00 +0200 (Tue, 31 Mar 2020)


[vagrant@fedora ooRexx.testSuite.svn]$ rexx -v
Open Object Rexx Version 5.0.0 r12034
Build date: Apr  1 2020
Addressing mode: 64
Copyright (c) 1995, 2004 IBM Corporation. All rights reserved.
Copyright (c) 2005-2020 Rexx Language Association. All rights reserved.
This program and the accompanying materials are made available under the terms
of the Common Public License v1.0 which accompanies this distribution or at
http://www.oorexx.org/license.html
[vagrant@fedora ooRexx.testSuite.svn]$ 



ooTest Framework - Automated Test of the ooRexx Interpreter

Interpreter:REXX-ooRexx_5.0.0(MT)_64-bit 6.05 1 Apr 2020
OS Name:LINUX
SysVersion: Linux 5.5.11-200.fc31.x86_64

Tests ran:  23061
Assertions: 382612
Failures:   2
Errors: 0

[failure] [20200401 11:06:08.985789]
  svn:r11985   Change date: 2020-02-27 21:24:37 +0100
  Test:   TEST_SEARCH_ORDER_TESTGROUP
  Class:  REQUIRES.testGroup
  File:   .../ooRexx/base/directives/REQUIRES.testGroup
  Line:   362
  Failed: assertSame
Expected: [[testGroup], identityHash="-140469326869153"]
Actual:   [[rex], identityHash="-140468748734097"]
Message:  this ::REQUIRES search order tests fails when run from within the 
same directory, but works as expected otherwise

[failure] [20200401 11:06:12.126584]
  svn:r11985   Change date: 2020-02-27 21:24:37 +0100
  Test:   TEST_SEARCH_ORDER
  Class:  CALL.testGroup
  File:   .../ooRexx/base/keyword/CALL.testGroup
  Line:   760
  Failed: assertSame
Expected: [[testGroup], identityHash="-140469299983345"]
Actual:   [[rex], identityHash="-140469000821521"]

Interpreter:REXX-ooRexx_5.0.0(MT)_64-bit 6.05 1 Apr 2020
OS Name:LINUX
SysVersion: Linux 5.5.11-200.fc31.x86_64

Tests ran:  23061
Assertions: 382612
Failures:   2
Errors: 0

File search:00:00:01.178939
Suite construction: 00:00:01.467390
Test execution: 00:03:50.886738
Total time: 00:03:53.880083









___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel