Hi Rick,
I gave it a try with
svn checkout https://svn.code.sf.net/p/oorexx/code-0/sandbox/rick/rexxutil
oorexx.rick
svn info
Path: .
Working Copy Root Path: /opt/oorexx.rick
URL: https://svn.code.sf.net/p/oorexx/code-0/sandbox/rick/rexxutil
Relative URL: ^/sandbox/rick/rexxutil
Repository
For my rexxutil sandbox version, I'm able to get a clean build on Windows,
but on Linux, I get a crash running rexximage. I've tried debugging this
using ddd, but it doesn't really give my any useful information. I'd really
appreciate any assistance you can provide.
Rick
Syntactically, it would be a category of Expression term. So in the manual,
it would probably be described as a new section 1.11.7 following the new
array terms. Syntactically, it is a prefix '>' or '<' followed by a either
a simple variable symbol or a stem variable symbol (no compound). The
I'm working on updating rexxref and rexxp for Variable References and need
to dig deeper: syntactically, what is a Variable Reference?
We have symbols, terms (plain, message, and array terms) and expressions.
How do Variable References fit in?
I'm struggling, because
>a~namewont work, but
v
>
> * !!! 'lib94 *-* allInstances[.Context~stackFrames[1]] =
> .Context~stackFrames[1]~hasMethod("makeString").dylib'
> works as designed/expected or something is fishy ?
>
Hi Enrico,
this is to be expected. It's from a test case that runs (among many other
methods)