UA3MQJ

Erlang and Named Pipes

The intention of this post is to provide a solution (with examples) to a somewhat uncommon issue in Erlang. I hate searching for answers to the same problems over and over, and I had a hard time finding answers to this particular problem, so I wrote it all down once I figured it out. If one day you decide to read and write data through fifo's (named pipes) and then decide you want to read or write the other end of the pipe from Erlang, this post is for you.

The Problem

I wanted to read and write to a fifo from a C/C++ app and have an Erlang app communicate over the other end of that fifo. Put simply, Erlang doesn't really support what I was trying to do. You cannot just file:open/2 a fifo, or any special device for that matter, in Erlang and expect it to work. This is documented in Erlang's FAQ.

The Solution! ... ???

sofakingworld

.....
config :logger, :console,
  level: :debug,
  format: {LoggerFormatter, :format_log}, 

brweber2

defmodule Benum do
  defimpl Enumerable, for: BitString do
    def count(collection) when is_binary(collection) do
      {:ok, Enum.reduce(collection, 0, fn v, acc -> acc + 1 end)}
    end
    def count(collection) do
      {:error, __MODULE__}
    end
    def member?(collection, value) when is_binary(collection) do
      {:ok, Enum.any?(collection, fn v -> value == v end)}

0xYUANTI

-module(bench).
-compile(export_all).

%% Luke Gorrie's favourite profiling macro.
-define(TIME(Tag, Expr),
        (fun() ->
             %% NOTE: timer:tc/4 does an annoying 'catch' so we
             %% need to wrap the result in 'ok' to be able to
             %% detect an unhandled exception.
             {__TIME, __RESULT} =