[erlang-patches] [patch] binary to/from integer
Fri Jan 11 13:21:19 CET 2013
And if it's supposed to create a binary representation of the integer as in
then I really don't see the need.
----- Original Message -----
> From: "Robert Virding" <>
> To: "Anthony Ramine" <>
> Cc: "erlang patches" <>
> Sent: Friday, 11 January, 2013 1:09:48 PM
> Subject: Re: [erlang-patches] [patch] binary to/from integer
> I missed the beginning of this discussion but is it supposed to do
> If so I fail to see a pressing need.
> ----- Original Message -----
> > From: "Anthony Ramine" <>
> > To: "Bob Ippolito" <>
> > Cc: "erlang patches" <>
> > Sent: Friday, 11 January, 2013 11:42:45 AM
> > Subject: Re: [erlang-patches] [patch] binary to/from integer
> > I disagree. Making it the big endian encoding of that integer is
> > something
> > that is already covered by OTP (binary:encode_unsigned/1 and its
> > friends),
> > and as you say, it's a *encoding* operation, not a type conversion.
> > Naming
> > this new BIF "integer_to_binary" isn't more confusing than
> > "atom_to_binary".
> > --
> > Anthony Ramine
> > Le 10 janv. 2013 à 23:13, Bob Ippolito a écrit :
> > > The purpose of integer_to_binary still isn't totally obvious from
> > > the name or output type, maybe it's digits, maybe it's the big
> > > endian encoding of that integer (which is closer to the behavior
> > > of binary_to_term / term_to_binary). For the more seasoned Erlang
> > > developer, I think they would expect it to behave like
> > > integer_to_string, but what about newer users?
> > _______________________________________________
> > erlang-patches mailing list
> > http://erlang.org/mailman/listinfo/erlang-patches
> erlang-patches mailing list
More information about the erlang-patches