Bonjour Jean Louis,
On 11.07.2024 08:37, Jean Louis Faucher wrote:
Guten Tag Rony
+1 globally
:-)
I still continue to think that the point 1 for guarded methods could be
reworded.
Your description makes reference to 2 guarded methods:
* the “caller”: A guarded method can invoke...
* the “called”: If that other method is guarded...
In the point 2, it’s clear that the focus is on the “called”: Invoking a guarded method from
another thread
The purpose of the point 1 is to explain when the counter is incremented.
That doesn’t depend on the “caller” being guarded, but it depends on the thread
of the caller.
Maybe the point 1 should start like that:
Invoking a guarded method from the same thread …
Point 1 would express that, however the information about the same thread is at the end of the
sentence (probably due to my German speaking background) and not at the beginning which may be
irritating.
As it seems to make it clearer, I will change that point as you suggest.
While doing so, I would add another point on both variants that explain guard on|off in their
context and link to the explanation where "guard on|off when condition" gets explained in the
documentation.
The question would be also where to place this information in the ooRexx
reference?
Best regards
---rony
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
