mirror of
https://github.com/Xahau/xahaud.git
synced 2026-07-29 10:00:09 +00:00
3a4c1dd053
Implements two community requests (chrische) under the existing, never-activated featureNamedHooks amendment: - HookNames: an STArray of NamedHook wrappers lets one transaction trigger multiple distinct named hooks (generalises the single HookName selector). - cron-carried selectors: CronSet persists HookName/HookNames onto the cron object; the validator-injected, zero-fee ttCRON pseudo-txn carries the selector to the owner hook chain and across recurrences, so a cron can target specific named hooks without a separate triggering transfer. all new selector behaviour is gated behind featureNamedHooks; with the amendment disabled the deterministic ledger output is byte-identical to the released binary. callback dispatch and again-as-weak replay disambiguate duplicate-hash hook slots by emit-time chain position, falling back to hash matching when the slot is unambiguous.
protocol
Classes and functions for handling data and values associated with the XRP Ledger protocol.
Serialized Objects
Objects transmitted over the network must be serialized into a canonical format. The prefix "ST" refers to classes that deal with the serialized format.
The term "Tx" or "tx" is an abbreviation for "Transaction", a commonly occurring object type.
Optional Fields
Our serialized fields have some "type magic" to make optional fields easier to read:
- The operation
x[sfFoo]means "return the value of 'Foo' if it exists, or the default value if it doesn't." - The operation
x[~sfFoo]means "return the value of 'Foo' if it exists, or nothing if it doesn't." This usage of the tilde/bitwise NOT operator is not standard outside of therippledcodebase.- As a consequence of this,
x[~sfFoo] = y[~sfFoo]assigns the value of Foo from y to x, including omitting Foo from x if it doesn't exist in y.
- As a consequence of this,
Typically, for things that are guaranteed to exist, you use
x[sfFoo] and avoid having to deal with a container that may
or may not hold a value. For things not guaranteed to exist,
you use x[~sfFoo] because you want such a container. It
avoids having to look something up twice, once just to see if
it exists and a second time to get/set its value.
(Real example)
The source of this "type magic" is in SField.h.