In columns, the order of the literals limits the decimal positions of a field #668
Loading…
Reference in a new issue
No description provided.
Delete branch "rpg-9-az-pool-order-scale-20261029"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In columns, the order of the literals limits the decimal positions of a field
The literals of the source are a run of constants sorted by their source text
(
rpg_source_scale.zig, d7-lits). A free-form source proves a scale by thetype keyword digit that
packed(7:3)pools; fixed D lines pool none, so apacked or zoned field of a fixed-form program kept 0 decimal positions unless
an edit mask proved them. That was enough while the 0-scale text sorted where
the original did, but r6e-ho-nooflind-two has
Amt 7P 3 INZ(12.345): itsdigits 12345 sort before Total's 1234.56 in the object, and
INZ(12345)sortsafter it, so the rebuilt pool differed (ROUND9 4.2i, ftwin19).
In columns,
scale_mod.narrowedfirst fixes the texts of the fields whosepositions another fact proves (an edit mask) and applies the order of the run
again;
scale_mod.smallestReadingthen gives each field with no other proofthe smallest scale that the order permits. Every permitted scale gives the
same object, because the creation data holds no decimal point: Amt becomes
7P 1 INZ(1234.5), which matched the object twice on the host.Gates