Files
xahaud/src/ripple/protocol
Denis Angell de03278927 cont tests..
2023-06-15 23:01:10 +00:00
..
2023-06-15 23:01:09 +00:00
2023-02-07 16:15:57 +00:00
2020-12-04 12:45:12 -08:00
2023-05-22 15:06:05 +02:00
2023-06-15 23:01:10 +00:00
2022-02-07 11:06:33 +00:00
2022-03-04 14:16:59 -08:00
2022-04-06 13:29:48 -07:00
2023-02-06 09:03:11 +00:00
2022-04-06 13:29:48 -07:00
2022-04-06 13:29:48 -07:00
2023-03-21 08:01:47 -07:00
2020-09-01 08:58:57 -07:00
2022-08-25 08:38:28 -07:00
2023-05-22 15:06:05 +02:00
2021-01-09 13:50:07 -08:00
2015-07-29 11:56:05 -04:00
2022-03-09 15:51:39 -08:00
2022-04-06 13:29:48 -07:00
2023-05-22 15:06:05 +02:00
2022-03-22 13:49:41 +00:00

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 the rippled codebase.
    • 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.

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.