DAS Script Version Compatibility and Source Errata
Read conflicting examples critically and maintain a capability matrix.
Authority requires traceability
Prerequisite: order types and object inspection. This is an independently authored FennEdge course, not a DAS certification. Its baseline is the official Advanced Hotkey Guide and Order Objects V2, both dated June 27, 2025, checked again September 11, 2026. The latter is five pages and largely overlaps the former’s short-form-order section; two overlapping documents are not two independent runtime validations.
Keep these evidence states separate
Documented means a source gives the contract. A course design is our composition of documented primitives. Client-tested means exact code was run on a recorded build. Broker-tested adds a specific account, route and observed external result. This edition contains documented contracts and course designs; the DAS snippets are not client-tested by FennEdge. Web rendering tests validate the teaching website, not DAS execution.
Concrete source conflicts
| Source | Observation | Course handling |
|---|---|---|
| V2 p. 4 | Some Sell stop-limit / SLP headings show B in code | Do not infer direction from heading; inspect Side |
| V2 p. 5 | Range prose and numeric examples disagree on price order | No guessed executable correction |
| Advanced p. 10 | Quote example changes variable names; cancellation list prints FIST | Use consistent owned names; verify ambiguous flag |
| Advanced pp. 31, 28 | ShowObj spelling appears alongside ShowObject elsewhere | Course uses ShowObject where documented; no blanket alias claim |
| Advanced p. 35 | SYMBOL assignment and SYMB reading appear together | Prefer documented GetTicker; verify actual object fields |
| Advanced p. 33 | GetAlertObj appears in a heading without a full lookup contract | Do not invent lookup arguments |
A conflict log should include the exact source revision and what remains unresolved, not silently replace source text.
Build a capability matrix
For each feature record build, broker, window type, prerequisites, exact script, expected result, actual result and date. Include the 5.7.9.9+ statement for combined order filters as a feature-specific claim. The one-order-per-second note in the 2025 guide is likewise versioned. A newer date on a knowledge-base page is not proof every installed client implements that behavior.
An executable compatibility probe
$feProbe = NewUserObj();
$feProbe.Set("revision", 1);
$feProbe.Set(0, 7);
MsgBox($feProbe.Get("revision"), $feProbe.Get(0));
$feProbe.Del(0);
$feProbe.ShowObject();
Exercise and worked answer
A source says Sell but its code uses B. What should the course do? Answer: preserve both observations, explain the conflict, avoid a silent correction and verify the intended Side using the current builder and object inspection. Do not submit a real order to discover what a typo means. For the probe above, expect revision 1 and value 7 before deletion; afterward inspect the absence of key 0 without assuming a missing Get return value.