I guess what he was meaning is that in Erlang in most cases you can work with strings as iolists.
Maybe here you can find a bit better explanation: http://erlang.org/pipermail/erlang-questions/2012-May/066590...
Right. This is like the POSIX features writev() and 'struct iovec'. Essentially all of Erlang's binary output primitives are happy to take an iolist/iovec instead of a plain string and this means fewer concatenations and/or system calls. Good feature.
iolists map nicely to gather-write writev(),
but unfortunately there is no Erlang primitives for scatter-read readv()
This isn't entirely true, see file:pread/2 for how to do it with a file. We lack a binary:pread/2 though :)
thanks for pointing it out,
looks like it will not work with sockets though.
Also spec says that it will return list of either strings or binaries, not exactly iolist.
> Also spec says that it will return list of either strings or binaries, not exactly iolist.
It's a proper subset of iolists, since it reads from flat data (a file) there isn't much sense in its adding arbitrary amounts of nesting to it.
He's talking about iolists (concatenating strings for IO, which is the most common use case and the one needed for e.g. templates), not straight strings.
I wonder how many times that's need to be said until it sinks in? This is the third time and I didn't even go through half of comments yet...
Many times :)
writev() is hard to grasp.
Just check your /usr/lib/erlang/lib/stdlib-xxx/src/string.erl, and you'll find this:
and "++" is obviously a O(N) operator.But yes, string concatenation is somewhat faster than other languages that represent strings with arrays of characters. Because in Erlang, it's O(N), while in others it's O(N+M), where N is the length of the first string and M is the length of the second.