Add ability to propagate numeric settings to called routines and methods using ::options
Add ability to override package options at runtime
Completed the Package's globalOptions tests with [r13031].
20251022 Complete the Package's globalOptions tests, cf. [feature-requests:#857]
20251021 Move image down a little bit for better legibility.
20251021 Fix a typo and make options purpose better understandable.
Docs committed with [r13028]
Add ability to override package options at runtime
Docs committed with [r 13028].
20251021 Complete docs for [feature-requests:#857]
Add command line option for overriding package options
Implemented with [r13027].
20251020 Implement [feature-requests:#859], run 'rexx' to learn about options.
Add command line option for overriding package options
Settings like 'numeric digits' or 'signal on' are always local to methods It's even local to subroutines. Example: call nutsup /* get firmware and more */ numeric digits 15 /* fails if in nutsup: */ Took quite a while untuil I grasped numeric digits can't be set in a setup subroutine.
Take a look at the ::OPTIONS directive if you want package-wide scope for your NUMERIC DIGITSsetting. For example, ::OPTIONS DIGITS 18 applies to the whole package and ensures that (if you don't modify it inside a code body), DIGITS() = 18 everywhere.
As far as I have observed, it will be 9, the default. With or without 'use local'. Settings like 'numeric digits' or 'signal on' are always local to methods, even in the same class.
Good afternoon! I'd like to clarify some information about the NUMERIC DIGITS scope. I have a class with several methods that call each other, like this: Class Method 1 use local Method 2 use local If I set "NUMERIC DIGITS 18" in "Method 1" and then call "Method 2," what will the precision be in "Method 2"? The same question applies without the "use local" command in methods, when class variables are not accessible within the method.
Uploading a patch that fixes this bug.
Here's a patch for this bug.
Uploading a patch that fixes this bug
Uploading a patch which fixes this bug.