this runs before commands, not after the whole command line (before prompt is displayed).
my personal bash history tweak suit is based on this.
with a load of complexity of course, because the DEBUG trap is also triggered before each PROMPT_COMMAND commands and on every simple command within the issued command line.
so the above example would record each command of a pipeline separately.
The article says:
"So when you change what + means, it will throw away all those methods it compiled with the old definition. Poof. Gone."
Is this enough? What about the function's side effects?
If the function changed 1000 variables with the wrong + definition, is it going to roll them back?
Another 1 minute lookin... multiplication on every byte.. really?
If this is supposed to be fast, get one big buffer for the words. Get another if you run out.
The hash function can be the word itself for words up to length 8.
Longer words would need a mult per 8 bytes.
You can do branchless strchr.
Roll your own memmove - just always copy 24 bytes and terminate at the length you already know.
The whole point of using C or C++ is that you can do non idiomatic things when you have to.
That's not the point. It's perfectly safe and there's nothing else in C.
The point is you don't have to call this function for every single word. It takes time and pointer increment doesn't
Ooo... spooooky pointers... ancient prophecies speak of the Earth splitting in half and swallowing everyone who's ever thought about allocating memory.
