srdusr
aboutsummaryrefslogtreecommitdiffstats
path: root/include/wireframe/search.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/search.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/search.hpp')
-rw-r--r--include/wireframe/search.hpp26
1 files changed, 0 insertions, 26 deletions
diff --git a/include/wireframe/search.hpp b/include/wireframe/search.hpp
deleted file mode 100644
index 4cb9203..0000000
--- a/include/wireframe/search.hpp
+++ /dev/null
@@ -1,26 +0,0 @@
-#pragma once
-
-#include <algorithm>
-#include <cctype>
-#include <string>
-
-// A display filter, distinct from -f's capture filter (wireframe/filter.hpp):
-// -f decides what's captured - and, combined with -w, what's written to
-// disk. This decides what's shown, without touching either. Same
-// distinction Wireshark draws between a capture filter and a display
-// filter, just without the display filter's expression language - a
-// plain case-insensitive substring match over the packet's summary line
-// is enough for "find the packets mentioning this host/port", which is
-// the actual use case.
-namespace wireframe {
-
-inline bool matches_search(const std::string& haystack, const std::string& needle) {
- if (needle.empty()) return true;
- auto it = std::search(haystack.begin(), haystack.end(), needle.begin(), needle.end(),
- [](unsigned char a, unsigned char b) {
- return std::tolower(a) == std::tolower(b);
- });
- return it != haystack.end();
-}
-
-} // namespace wireframe