The praise goes to Jon, not to me ;-)Von meinem iPhone gesendet P.O. Jonsson
Dear P.O.,
thank you *very* much for your feedback!
On 12.10.2025 10:09, Sahananda wrote:
The sentence:
This method allows for getting at the currently set
package options, which can be explicitly set using the
::options directive.
in my opinion could be expressed better as:
This method retrieves the current set package
options, which can be set explicitly using the
::options directive.
Well, this new method will allow to do what ::options allows for,
just at runtime ("dynamically") and therefore one can use it to
change a package wide options setting, e.g.
pkg=.context~package -- get at this routine's/method's package object
-- turn trace results on for the next invocations of routines and methods from this package
pkg~options("trace","results")
-- change numeric digits to 21
pkg~options("digits",21)
But you are right the sentence is difficult and not clear and
should be improved.
In the sentence, 'be explicitly set' would be a split
infinitive which is not encouraged (but often appears - most
famously in Star Trek), so I have reversed the order of those
two words.
I'm not sure what meaning is added by the word
'explicitly', so you might think it even better to omit that
word altogether.
The information should remain, that one can a) query the option
settings in effect for the package, and b) change these option
settings for the package, which will take effect on the next
invocation of a routine or method from that package. So maybe
someone can come up with better formulations that would carry that
information in an easy graspable manner?
---rony
Committed the documentation with [r13021]:
<0LoN0r6eayQXoDuc.png>
Here the RFE-link: <https://sourceforge.net/p/oorexx/feature-requests/857/>.
---rony
On 11.10.2025 19:20, Rony G. Flatscher wrote:
Here is a draft of the planned documentation of the
Package's new options method:
Method „Options“
This method allows for
getting at the currently set package options, which
can be explicitly set using the ::options directive.
Sending the options message
without an argument will return a string encoded as
an ::options directive denoting all the current
settings of the package, e.g., ”::OPTIONS DIGITS 9 FORM
SCIENTIFIC FUZZ 0 ERROR CONDITION FAILURE CONDITION
LOSTDIGITS CONDITION NOSTRING CONDITION NOTREADY
CONDITION NOVALUE CONDITION PROLOG TRACE NORMAL“
Sending the message options
with one argument, the option argument, will return
the current setting for that particular option. If a
second argument is supplied, then the option will
get set to that value, and the previous value is
returned.
The following table lists the
option names and the values they accept:
|
Option
|
Value
|
|
Digits
|
9 (a whole
positive number)
|
|
FUzz
|
0 (a whole
number, must be smaller than digits)
|
|
FOrm
|
Scientific,
Engineering
|
|
|
|
|
Conditions:
|
|
|
All (only for
setting all conditions at the same time)
|
Condition,
Syntax
|
|
Error
|
Condition,
Syntax
|
|
FAilure
|
Condition,
Syntax
|
|
Lostdigits
|
Condition,
Syntax
|
|
NOString
|
Condition,
Syntax
|
|
NOTready
|
Condition,
Syntax
|
|
NOValue
|
Condition,
Syntax
|
|
|
|
|
Prolog
|
Prolog, Noprolog
|
|
Trace
|
All, Commands,
Error, Failure, Intermediates, Labels,
Normal, Off, Results
|
Not being a native English speaker, any suggestions to
improve the text are highly appreciated!
---rony
_______________________________________________Oorexx-devel mailing list[email protected]https://lists.sourceforge.net/lists/listinfo/oorexx-devel
|
