loop: no stop condition, and the for_each_ne unrolling as the recommended form
The page described an optional boolean stop parameter that would end the loop early. The
engine has never had one: the only trace in the code was a type check on a stopValue item
behind a branch that could not run, removed in GeoDMS 485d447fb. The page now says what the
function does: number instantiations, each fed the nextValue of the one before it, lastIter
referring to the last.
The example is corrected as well: the loop call sat inside the template it instantiates,
and the iteration parameter was uint32 where the function binds a uint16; checked against
the tst Operator configuration, loop/lastIter/results/LoopWaarde is 4.
New section: the same chain with for_each_ne over an iteration domain, the previous state
named per iteration by MakeDefined(name[sub_or_null(id(.), 1)] + '/ResultingState',
'StartingState') and the template instantiated with it, which puts the names, the arguments
and the carried state under the configuration's control. The example was run as written
(GeoDMS 20.21.0 build of 485d447fb): PrevName is StartingState for the first iteration and
Iter0/ResultingState for the second, and the last state is 100 * 1.1^5. Links to the convex
hull example script, which already uses the pattern.
MetaScript-functions: the one-line description of loop no longer mentions a stop condition.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
#1259 The do function: a chain of calculations that run side by side, and the file set example
do(item, string) is expand after item has been calculated, and nested do calls form one
calculation whose arguments are demanded together, leftmost first. That is the way to ask for
concurrency, where ExplicitSuppliers updates its list one entry at a time. The page states the
two conditions (links must be data items, the chain must be demanded as data), the memory rule
(a chain holds its arguments until it is done, so batch), and the BAG file set configuration
with its measurements: 156 s against 310 s on the 2026-08-08 pand extract, 8.4 GB against 2.4 GB,
and 68 GB for one unbatched chain over all 50 file sets. Cross-linked from the function indexes,
ExplicitSuppliers and parse_xml.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Complete coverage documentation: variant bullets for every tested operator group (typed unique/select/combine/union_unit/join/count/sum/pcount/unique_count/modus_count/district families, griddist combinations, potential backends, points2* argument forms, bp morphological variants, dyna_*_uint64, null point/string constants, fast variants, dist_info_eq/ne, spatialIndex, bitxor, collect_by_org_rel, ordinal) + new pages iterate, subindex, rlookup_with_null; worklist: every testable operator group tested and documented (606 of 606 on 20.13)
Documentation complete for all tested operators: variant bullets on category pages (argmax/argmin/sum/reg_count/select_uint*/null_*/corr/cov/unique_with_null/asExprList_with_null/dyna_segment_with_ends/discrete+greedy+needy_alloc family), links for existing pages (mid, outer_single_polygon, geos_buffer, sqrdist, exp, log, Void, subitem), new pages (needy_alloc, DocData, DocStorageManagers, sequence_element_count, ordererd_union_data, canyon, ClassifyNonzeroEqualCount, ClassifyNonzeroEqualInterval); worklist: 455 of 455 documented operators covered on 20.8.0
Fix migration artifacts, typos and dead links across the wiki
Sweep of all 867 pages: MediaWiki-to-GitHub migration damage repaired
(wikilink artifacts, reversed link order, broken code blocks, image
links restored as embeds), 2200+ typo/grammar/dead-link fixes, and
remaining CalcCache references removed or marked version-historical.
Factual example errors corrected where unambiguous (a.o. Boundcenter,
Ge_or_rhs_null, Capacitated_connect, Dpoint, Modus).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Updated MetaScript functions (markdown)
Updated MetaScript functions (markdown)