Rick, Mark
Yes you're right, I used: say .rexxqueue~new(!new) giving !NEW and
assumed it was the queuename, using
say .rexxqueue~new(!new)~class gave indeed The RexxQueue class
Thanks for the correction
Ruurd
On 21-6-2013 21:05, Mark Miesfeld wrote:
Rick is still too quick for me.
On Fri, Jun 21, 2013 at 11:53 AM, Ruurd Idenburg <ru...@idenburg.net
<mailto:ru...@idenburg.net>> wrote:
Is it me not understanding, or is the RexxQueue class indeed unusable,
since none of the class methods returns an instance and therefore none
of the instance methods can be used?
It's your understanding. I haven't used that class much, if at all.
So I looked at the test group for RexxQueue. Here is some code from
one test case:
q = .RexxQueue~new('testQueue')
s = 'test string'
s2 = 'test string2'
q~queue(s)
q~queue(s2)
self~assertEquals(2, q~queued, 'subTest19: Queue 2 adds two lines')
self~assertEquals(s, q~pull, 'subTest20: Queued line correct
FIFO')
q~delete
The self~assertEquals is not going to work outside of the test case,
but you should be able to get the idea for q~queued and q~pull.
--
Mark Miesfeld
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
--
Ruurd Idenburg
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
