It most certainly IS an assignment. The stem variable rr. is set to
contain a reference to the same stem object referenced by the stem variable
r. ooRexx does not have a concept of variable aliasing. This is the same
assignment mechanism that allows USE ARG to work or returning a stem object
In REXX version 1 of this RC-task:
http://rosettacode.org/wiki/Hofstadter_Figure-Figure_sequences#REXX
there is this statement
rr.=r.;
which shows a severe incompatibility.
With Regina, this program runs fine.
With ooRexx it fails!
The reason is that the above is NOT an assignment
Hi Walter,
first the example on Rosetta code you cite as a real life example comes from
your special friend,
who tries to write Rexx as if it was Assembler at times. So you should ask
yourself how a real
life example that would be.
(I have never seen a classic Rexx program that would use that
I wa surprised to 'find' it in real life!
And a little sentence right at the description of 'assignment' about this
special
treatment could help.
Such as mentioning the special treatment of the case when source and targed are
stems,
And the feature of a.=fun() fun:... with return res. was news
Thank you, Rony; This is a classic example of ...what a thing is, and what
a thing's name is Charles Lutwidge Dodgson explained it all 150 years
ago.
Walter, between Dodgson and Godel (pardon the spelling; my keyboard does
not have an umlaut) language designers and implementers face an
Some notes about Publican under MacOs, and a question for Erich at the end
of the mail.
According to my tests, Publican 4.2 4.3 is not producing good results
under MacOs.
I use Publican 4.1.3 which works good.
The pdf files look similar to a pdf that I downloaded a few month ago from
the build
Publican ooRexx brand :
I made a change in en-US/Notices.xml, committed to svn
The same change has been propagated to the the file
publish/oorexx/en-US/Notices.xml by make. This file has now the svn status
'modified'.
Do we need the directory 'publish' in svn ? Seems to be a generated
directory.
