The problem is with rxqueue. If you add a line to the script to display the value of the queued() function prior to the loop you will see that it is equal to zero.

Tested with the 4.0 release on Fedora 11.

David Ashley

On 10/19/2009 01:26 AM, Rony G. Flatscher wrote:

Rick McGuire wrote:
I just did a fresh build on Fedora 11 and except for including that
error information on the end, all of the version information is
getting printed out.  Are you using an official released version or
your own build?
Using my own build from trunk. The problem is that running the following script:

    -- address cmd
    "rexx -v | rxqueue"
    bitness=0
    do while queued()>0
        parse pull hint ":" val .
        if hint="Addressing Mode" then bitness=val
    end
    say "bitness:" bitness
will not yield the desired result on Unix (bitness will always remain set to 0).

However, studying the code you changed I could come up with a variant that works:

    -- address cmd
    "rexx -v 2>&1 | rxqueue"
    bitness=0
    do while queued()>0
        parse pull hint ":" val .
        if hint="Addressing Mode" then bitness=val
    end
    say "bitness:" bitness
I.e. redirecting stderr to stdout such that that is piped to rxqueue as well.

---rony


On Sun, Oct 18, 2009 at 5:26 PM, Rony G. Flatscher
<[email protected]>  wrote:
Hi there,

just came up with testing a little script which is supposed to find out the
bitness of the installed ooRexx interpreter using "rexx -v | rxqueue" and
then parsing the "Address mode:" line. This works fine on Windows, but on
32-bit Linux it always brings up the following error message:

Syntax is "rexx [-v] filename [arguments]"
or        "rexx [-e] program_string [arguments]"


Without being able to get at the bitness, it is unfortunately not possible
to have script figure that out and copy the dll/shared lib to the
appropriate place!
:-(

Unfortunately, the RFE related to this very same use-case
<https://sourceforge.net/tracker/?func=detail&aid=2787342&group_id=119701&atid=684733>
has not been made available yet either.

---rony


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference


_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to