] [20190202 22:29:47.760694]
svn: r11562 Change date: 2018-12-03 23:45:29 +0100
Test: TEST_REXXC_ONE_ARG
Class: rexxc.testGroup
File: /export/home/agrellum/test/ooRexx/utilities/rexxc/rexxc.testGroup
Line: 100
Failed: assertTrue
Expected: [1]
Actual: [[0], identityHash
The problem is you are setting the variables in the wrong object. The API
returns references to the object variable in the currently active object,
which in this case is the tester object instance.
I suggest adding a couple of attributes to the MethodTester class that will
give you variables you ca
>
> as soon as the build completes
>
Is building slow on Windows? If you're building with nmake, you might
consider using jom, which builds multi-core.
See
https://sourceforge.net/p/oorexx/wiki/how-to-build-oorexx/#multi-core-builds
.
we might need a GetContextVariableReference() API on the call a
On Sat, Feb 2, 2019 at 9:42 AM Erich Steinböck
wrote:
> We have five native Variable Reference APIs. Three of them are available
> in all the usual contexts: Thread/MethodCall/Exit
> IsVariableReference, VariableReferenceName, VariableReferenceValue
>
> But two of them are restricted to one conte
We have five native Variable Reference APIs. Three of them are available in
all the usual contexts: Thread/MethodCall/Exit
IsVariableReference, VariableReferenceName, VariableReferenceValue
But two of them are restricted to one context:
GetObjectVariableReference available in method context only
S
Ahthat's what we call "a bug"! Looks like there is a small problem with
the code that recognizes instruction types.
Rick
On Sat, Feb 2, 2019 at 8:31 AM Erich Steinböck
wrote:
> >a~namewont work, but
>>>
>>
>> Why do you say this won't work?
>>
>
> It doesn't parse (note that there is no
>
> >a~namewont work, but
>>
>
> Why do you say this won't work?
>
It doesn't parse (note that there is no say instruction).
~~~
rexx -e ">a~name"
1 *-* >a~name
Error 35 running INSTORE line 1: Invalid expression.
Error 35.1: Incorrect expression detected at ">".
~~~
___
To make sandbox/rick/rexxutil compile with gcc 5.4.1 I had to apply a few
changes
~~~
Index: interpreter/classes/NumberStringClass.cpp
===
--- interpreter/classes/NumberStringClass.cpp (revision 11704)
+++ interpreter/classes/Number
>
> how did you determine this?
>
On Linux you'd use gdb. We have a short Wiki page how to debug on Linux at
https://sourceforge.net/p/oorexx/wiki/how-to-debug-oorexx/
Like this:
~~~
rexxutil-debug$ gdb bin/rexximage
(gdb) run
Starting program: rexxutil-debug/bin/rexximage
[Thread debugging using
I made a debug on MacOs with Xcode (after fixing the compile error).rexximage(30751,0x10075b380) malloc: *** error for object 0x101801800: pointer being freed was not allocated#0 0x7fff7b350b66 in __pthread_kill ()#1 0x0001007540f0 in pthread_kill ()#2 0x7fff7b2ac1ae in abort ()#3 0x000
Hmmm, it's strange I'm not seeing a similar problem on Windows. It sounds
plausible that's the problem. For my education, how did you determine this?
Rick
On Sat, Feb 2, 2019 at 6:00 AM Jean Louis Faucher
wrote:
> FileNameBuffer
> You should create a copy constructor and a copy assignment opera
FileNameBuffer
You should create a copy constructor and a copy assignment operator.
With their default implementation created by the compiler, the buffer is copied
as-is, and you have multiple delete of the same buffer.
FileNameBuffer(const FileNameBuffer &other);
FileNameBuffer &operat
oops, I still had some uncommitted code.
Rick
On Fri, Feb 1, 2019 at 7:57 PM Enrico Sorichetti via Oorexx-devel <
oorexx-devel@lists.sourceforge.net> wrote:
> 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 in
13 matches
Mail list logo
