On 22.02.2012 10:47, Rony G. Flatscher wrote:
On 19.02.2012 15:16, Rick McGuire wrote:
On Sun, Feb 19, 2012 at 8:48 AM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at wrote:
After having implemented and successfully tested the RXSIO, RXNOVAL and
RXVALUE exits (i.e. exit handlers in Java
On 21.02.2012 21:37, Rick McGuire wrote:
I don't see anthing obviously wrong here. Provide a sample program so
I can recreate this, and I'll take a look at it.
Also, just for the record for others who read this thread and are interested in
the final result:
RXOFNC/RXEXF setting of flags works
Can you tell me where the latest PDF builds are?
They used to be at http://build.oorexx.org/builds/docs/
http://build.oorexx.org/builds/docs/, but there's nothing there now...
Many thanks,
Oliver
--
I think David is doing some work on the build machine and it is not
currently building the docs.
I'll send the latest oodguide.pdf and oodialog.pdf to you in a separte
e-mail. If anyone else would like a copy, just e-mail me at my gmail
address.
--
Mark Miesfeld
On Thu, Feb 23, 2012 at 7:42
Hi,
I don't know if this is a bug or programmer error. It is an unexpected result
for me. When I use the statement SAY I:X I expected the same results as when
I use the statement SAY I:L but ooRexx thinks I'm trying to use a hex number.
Am I not using Rexx correctly?
Bruce
In a string abuttal the trailing character x has a higher precedence
than other characters. Thus Rexx will always assume that a string
constant with an immediate trailing x will assumed to be a hex string.
This is the way it has always been.
David Ashley
On 02/23/2012 10:38 AM, CVBruce
You can avoid it by using the abbutal operator wherever you use a variable
named x (or b)
I=1;X=2; Say I:||X;
hth,
Jon
On 23 February 2012 16:54, CVBruce cvbr...@gmail.com wrote:
Ok, Thanks.
On Feb 23, 2012, at 8:47 AM, David Ashley wrote:
In a string abuttal the trailing character x
