On 11/22/2013 02:55 PM, Jeroen Bollen wrote:> On Friday, 22 November
2013 at 21:17:56 UTC, monarch_dodra wrote:
>> On Friday, 22 November 2013 at 19:44:56 UTC, Jeroen Bollen wrote:
>>> On Friday, 22 November 2013 at 19:22:16 UTC, Ali Çehreli wrote:
import std.bitmanip;
import std.system
On Friday, 22 November 2013 at 21:17:56 UTC, monarch_dodra wrote:
On Friday, 22 November 2013 at 19:44:56 UTC, Jeroen Bollen
wrote:
On Friday, 22 November 2013 at 19:22:16 UTC, Ali Çehreli wrote:
import std.bitmanip;
import std.system;
void main()
{
ubyte[] data = [ 1, 2, 3, 4 ];
assert(da
On 11/23/2013 08:36 AM, Jeroen Bollen wrote:
> So if I have a byte array [0, 0, 1, 0], and I read a ushort from it
> twice, I will get this?
>
> ubyte[] arr = [0, 0, 1, 0];
> arr.read!(ushort, Endian.littleEndian); // == 0
> arr.read!(ushort, Endian.littleEndian); // == 1
> arr.length; // == 0
Y
On Saturday, 23 November 2013 at 15:21:02 UTC, Ali Çehreli wrote:
On 11/23/2013 04:08 AM, Jeroen Bollen wrote:
On Friday, 22 November 2013 at 23:12:25 UTC, Ali Çehreli wrote:
That means that the slice itself cannot be modified, meaning
that it
cannot be consumed by read. Can't work... :)
Why
On 11/23/2013 04:08 AM, Jeroen Bollen wrote:
On Friday, 22 November 2013 at 23:12:25 UTC, Ali Çehreli wrote:
That means that the slice itself cannot be modified, meaning that it
cannot be consumed by read. Can't work... :)
Why does read need to be able to change the byte array?
From the docu
On Friday, 22 November 2013 at 23:12:25 UTC, Ali Çehreli wrote:
That means that the slice itself cannot be modified, meaning
that it cannot be consumed by read. Can't work... :)
Why does read need to be able to change the byte array?
