In a project I'm working on I ran into the requirement of having some sort of persistent FIFO buffer or pipe in Linux, i.e. something file-like that could accept writes from a process and persist it to disk until a second process reads (and acknowledges) it. The persistence should be both across process restarts as well as OS restarts.
AFAICT unfortunately in the Linux world such a primitive does not exist (named pipes/FIFOs do not persist
| #!/bin/bash | |
| replacements=( | |
| "NanAsyncWorker/Nan::AsyncWorker" | |
| "NanAsyncQueueWorker/Nan::AsyncQueueWorker" | |
| "NanCallback/Nan::Callback" | |
| "NanSetInternalFieldPointer/Nan::SetInternalFieldPointer" | |
| "NanGetInternalFieldPointer/Nan::GetInternalFieldPointer" | |
| "NanNewBufferHandle\\(([^;]+);/Nan::NewBuffer(\\1.ToLocalChecked();" | |
| "(NanNew(<(v8::)?String>)?\\(\"[^\"]*\"\\))/\\1.ToLocalChecked()" |
Looking for support tables for HTML/CSS/JavaScript features or details on their implementation status in major browsers?
And then there’s Can I use…?.
| function bitCount(u) { | |
| // https://blogs.msdn.microsoft.com/jeuge/2005/06/08/bit-fiddling-3/ | |
| const uCount = u - ((u >> 1) & 0o33333333333) - ((u >> 2) & 0o11111111111); | |
| return ((uCount + (uCount >> 3)) & 0o30707070707) % 63; | |
| } |