srdusr
aboutsummaryrefslogtreecommitdiffstats
path: root/include/wireframe/byteio.hpp
diff options
context:
space:
mode:
authorsrdusr <[email protected]>2024-05-27 22:00:00 +0200
committersrdusr <[email protected]>2024-05-27 22:00:00 +0200
commitb565d7d9c47ca1ec5af0effd828431ee96027d60 (patch)
treefbe0c9c897e78f507443507354d5b1d8fb851099 /include/wireframe/byteio.hpp
parentfbedc55d5aa861c381701c9f913b34ee7ab57ec4 (diff)
downloadpacketeer-b565d7d9c47ca1ec5af0effd828431ee96027d60.tar.gz
packeteer-b565d7d9c47ca1ec5af0effd828431ee96027d60.zip
Rename project from wireframe to packeteer
Decided on the name after weighing alternatives in NAMES.md: packeteer (packet + -eer, "one who wields packets") fit the project's actual scope better than the wire/frame pun once it had grown into full L2-L7 dissection, reassembly, checksums, privilege dropping, and dual TUI/GUI frontends. No existing packet-capture project uses the name; the one real-world collision (Packeteer, Inc., a networking company acquired and folded into Blue Coat/Symantec by 2008) is long defunct. Mechanical rename throughout: CMake project/target names, the wireframe:: namespace and include/wireframe/ directory (git mv, history preserved), every #include path, CLI/GUI help text, and the project's own working directory. NAMES.md rewritten to record the decision instead of leaving stale self-referential etymology behind from the blind rename pass. Verified after every step: full rebuild (all four targets, no warnings) and the full test suite (128/128 cases, 366/366 assertions) both from a fresh reconfigure and again after the directory move.
Diffstat (limited to 'include/wireframe/byteio.hpp')
-rw-r--r--include/wireframe/byteio.hpp22
1 files changed, 0 insertions, 22 deletions
diff --git a/include/wireframe/byteio.hpp b/include/wireframe/byteio.hpp
deleted file mode 100644
index c37c29e..0000000
--- a/include/wireframe/byteio.hpp
+++ /dev/null
@@ -1,22 +0,0 @@
-#pragma once
-
-#include <cstdint>
-#include <span>
-
-// Manual big-endian reads instead of reinterpret_cast onto a packed
-// struct: network buffers from pcap aren't guaranteed aligned for
-// multi-byte integer types, so casting would be undefined behavior.
-namespace wireframe {
-
-inline std::uint16_t read_be16(std::span<const unsigned char> bytes, std::size_t offset) {
- return static_cast<std::uint16_t>((bytes[offset] << 8) | bytes[offset + 1]);
-}
-
-inline std::uint32_t read_be32(std::span<const unsigned char> bytes, std::size_t offset) {
- return (static_cast<std::uint32_t>(bytes[offset]) << 24) |
- (static_cast<std::uint32_t>(bytes[offset + 1]) << 16) |
- (static_cast<std::uint32_t>(bytes[offset + 2]) << 8) |
- static_cast<std::uint32_t>(bytes[offset + 3]);
-}
-
-} // namespace wireframe