Fomoxa

EN/VI

Byte inspector · RFC-0002

Type a value. See the bytes.

Encode any Fomoxa type, decode a payload, or put the correct bytes next to a known bug or your own implementation's output. Everything runs in your browser, and nothing is sent to a server.

Inspector

Examples

Compare

Syntax

Writing schemas and values

The schema notation is the one the RFCs use. It is a teaching notation, not an IDL: Fomoxa does not mandate one.

TypeValue examplesNotes
booltrue · falseNothing else. 1 is not a bool.
u8 … i64100 · -1 · 0x12345678 · 18446744073709551615Exact integers, range-checked. 64-bit values keep full precision.
f32 · f643.14 · -0.0 · Infinity · NaN · 0x7FC00001A 0x… value is the raw IEEE 754 bit pattern, so NaN payloads survive.
String"Xin chào" · "\u4E2D"Encoded as UTF-8. Lone surrogates are rejected.
Bytes"FF FE" · [255, 254]Hex text or a list of 0-255.
Array<T>[1, 2, 3] · [[1, 2], []]Any element type, nested arrays included.
enumWalk · PlayerState::Walk · 1enum E { A = 0, B }. Undefined values are rejected (N-040).
model{ id: 42, name: "Sword" } · [42, "Sword"]model M { id: u32; name: String }. Every field is required: Fomoxa has no defaults.

This page follows RFC-0002 and is checked against every RFC-0003 vector and the fomoxac accept/reject vectors. It is a learning tool, not a conformance suite: an implementation is Fomoxa Compatible only when it passes RFC-0003 itself.