Calculation-management, Why-GeoDMS, Home and four more: a result is reused while it is in memory
Seven pages said that within a session nothing is computed twice, or that only invalidated results
are recalculated. The engine releases the data of a result once nothing needs it any more
(AbstrDataItem::TryCleanupMemImpl, unless KeepData is set or the data is smaller than 128 bytes),
and a later request calculates it again: through the Python bindings, max(a) and min(a) read after
sum(a) recalculated a each time, and with KeepData on the attribute they did not. A calculation that
occurs in several places is shared, see calculation-cache.md (7f1bf520).
Calculation-management.md, Why-GeoDMS.md and Home.md (two sentences each), Strategic-decoupling.md,
Composite-function.md, Update-Mechanism.md and Management-of-dependencies.md now say that a common
calculation is shared and that a result is reused while it is in memory, kept longer with KeepData,
and link to the calculation cache page.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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 Composite function (markdown)
Updated Composite function (markdown)
Updated Composite function (markdown)