Short info:
The JSON.testGroup is failing on most *nixes, please have a look whoever wrote
it (Rony?)
The machine hosting all the VMs will be offline for a couple of days as of this
evening while being moved. Also the documentation build will be unavailable a
couple of days.
Jenkins itself wi
Hi P.O.,
On 11.02.2023 16:51, ooRexx wrote:
Short info:
The JSON.testGroup is failing on most *nixes, please have a look whoever wrote
it (Rony?)
Can you please make one or all of the logs available?
Without them it is a little bit hard to see what goes wrong... :)
Regards,
---rony
Just a quick question: what is the purpose of '!' in TRACE, have not seen
documentation about it.
In the case '!' is available then this could be used as an MT toggle?
---rony
On 09.02.2023 13:40, Rick McGuire wrote:
One other thing about the trigger character. The '?' and '!' triggers act as
Ad documentation: here a draft, meant for rexxref.pdf, chapter "12. Concurrency", suggesting of
adding a section at the end (activity, variable pool, locks already explained in that chapter):
--
12.5 Tracing Concurrent Execution
Each invoked routine and method routine will
'!' suppresses the issuing of commands. Generally used for
non-destructiive test runs. Not really used much but it takes up the '!'
symbol character.
Rick
On Sat, Feb 11, 2023 at 12:01 PM Rony G. Flatscher
wrote:
> Just a quick question: what is the purpose of '!' in TRACE, have not seen
> docu
Some comments:
1) the T and A columns are a bit redundant. We really only need a single
identifier for the thread, having two is just extra clutter.
2) The term activity is introduced here without explanation. It doesn't
really appear any other place in the documentation and is really more of an
i
A quick feedback about point 1:
The A column is in fact the activation identifier (RexxActivation).
It’s used to know which method/routine is executing the current line.
The name of this method/routine can be found by looking back in the trace the
first >I> for the current T.
In rexxref, “activat
In complement of the struct, this is how the infos are collected for each trace
line:
void GetConcurrencyInfos(Activity *activity, RexxActivation *activation,
ConcurrencyInfos &infos)
{
InterpreterInstance *interpreter = (activity ? activity->getInstance() :
NULL);
VariableDictionary *v
On 11.02.2023 18:16, Rick McGuire wrote:
Some comments:
1) the T and A columns are a bit redundant. We really only need a single identifier for the
thread, having two is just extra clutter.
2) The term activity is introduced here without explanation. It doesn't really appear any other
place in
Ah sorry I thought you had access.
@Rene’: can you set up an account for Rony? I am on the road for a couple of
days.
Von meinem iPhone gesendet
> Am 11.02.2023 um 17:48 schrieb Rony G. Flatscher :
>
> Hi P.O.,
>
>> On 11.02.2023 16:51, ooRexx wrote:
>> Short info:
>>
>> The JSON.testGroup
Similar comments: this extra information seems to be aimed at 'developers',
not users. A user seeing the proposed output would have no idea what it
means or what it's about. It's astonishing, in every sense.
To me this seems absolutely contrary to the Rexx principles. If developers
need this
Ugh, I don't find this to be helpful information at all. I can determine
that information just by looking at the thread numbers, the activation
number has no real connection to any concept in the interpreter.
Rick
On Sat, Feb 11, 2023 at 12:33 PM Jean Louis Faucher
wrote:
> A quick feedback abo
Rony,
If you have an account I can attach the privileges to it. You can make an
account on the machine itself.
René.
> On 11 Feb 2023, at 19:39, P. O. Jonsson wrote:
>
> Ah sorry I thought you had access.
>
> @Rene’: can you set up an account for Rony? I am on the road for a couple of
> da
On Sat, Feb 11, 2023 at 2:12 PM Mike Cowlishaw wrote:
> Similar comments: this extra information seems to be aimed at
> 'developers', not users. A user seeing the proposed output would have no
> idea what it means or what it's about. It's astonishing, in every sense.
>
> To me this seems abso
On Sat, Feb 11, 2023 at 12:53 PM Rony G. Flatscher
wrote:
> On 11.02.2023 18:16, Rick McGuire wrote:
>
> Some comments:
>
> 1) the T and A columns are a bit redundant. We really only need a single
> identifier for the thread, having two is just extra clutter.
> 2) The term activity is introduced
Thanks for your feedback.
> Ugh, I don't find this to be helpful information at all.
It's useful, I explained already why, see the CSV screenshot.
We don't have a rexx debugger like the orexx workbench showing the call stack.
But we can have at least the top-level of the call stack, everywhere.
>
16 matches
Mail list logo
