It would be helpful to pass a string or char[] buffer to a hypothetical RegExSearchB or RegExMatchB to be treated as binary, not textual, content. Thus the concept of lines would not exist (LF would not have special meaning), and . would match on any byte. I imagine that the length of the buffer would have to be passed as an argument to this new
Right now I have to work around by changing \x00 to \x01 in a loop before running the regex.
I use a regex to detect packet headers in a property list streaming protocol I’m reverse engineering. This is a heuristic until I figure out what the structural metadata that I’m skipping means.