[erlang-questions] what's happened in the shootout
Ulf Wiger (TN/EAB)
Mon Jun 18 18:44:44 CEST 2007
Now it seems ok again. It was problably just som
problem with the build on the AMD.
BTW, I made minor optimizations of the n-body
benchmark (Erlang Hipe #3), and then started
looking at the Mandelbrot. Requiring the program
to output one byte at a time is cruel and unusual
punishment for the lowly Erlang programmer.
Couldn't we introduce a BIF, erlang:put_chars(IoList),
(or possibly put_chars(stdout | stderr, IoList))
which simply writes the given bytes to stdout?
This would be similar to erlang:display(Term), but
without the auto-formatting of erlang terms, and
without the trailing newline.
I understand that there are great advantages to
using the standard IO subsystem, but it seems a bit
rude to not have raw output for those who want
that, and nothing else.
> -----Original Message-----
> From: erlang-questions-bounces@REDACTED
> [mailto:erlang-questions-bounces@REDACTED] On Behalf Of
> Bengt Kleberg
> Sent: den 18 juni 2007 10:19
> To: Erlang Questions
> Subject: Re: [erlang-questions] what's happened in the shootout
> On 2007-06-17 16:25, Mike McNally wrote:
> >> No, I was looking at this:
> >> all
> >> BR,
> >> Ulf W
> > It seems to be failing many of the benchmarks.
> where can i see this?
> is it on
> as mentioned above?
> Those were the days...
> EPO guidelines 1978: "If the contribution to the known art resides
> solely in a computer program then the subject matter is not
> patentable in whatever manner it may be presented in the claims."
> erlang-questions mailing list
More information about the erlang-questions