Re: Weird UFC and opCall issues

2015-01-03 Thread Darrell via Digitalmars-d-learn
Thanks for the feedback. With classes, you need to create an instance Need to read up classes vs struct. This bit of syntax was very intresting. /* Alternatively, you can move test() inside Test as a static opCall: static Test opCall() { return new Test(); } Then, the

Re: Weird UFC and opCall issues

2015-01-03 Thread Darrell via Digitalmars-d-learn
Seems when creating your own ranges they can't be a class. Must be a struct or Segmentation fault (core dumped) will follow. This works as long as Test is a struct. struct Test { @property int front() { return 2; } void popFront() { } enum bool empty = false; }; static asser

Re: Weird UFC and opCall issues

2015-01-03 Thread Darrell via Digitalmars-d-learn
Ooops. Test() wasn't valid. Still working to create a range object that iterates over an internal data struct. But this was may error. On Saturday, 3 January 2015 at 20:26:41 UTC, Darrell wrote: Fails with: t.d(34): Error: need 'this' for 'opCall' of type 'int()' Also opCall seems to be

Re: Weird UFC and opCall issues

2015-01-03 Thread Darrell via Digitalmars-d-learn
Fails with: t.d(34): Error: need 'this' for 'opCall' of type 'int()' Also opCall seems to be required to create a range. class Test { int opCall() { return 1; } @property int front() { return 2; } void popFront() { } @property bool empty() { return false;

regex on binary data

2014-12-31 Thread Darrell via Digitalmars-d-learn
So far attempts to run regex on binary data causes "Invalid UTF-8 sequence". Attempts to pass ubyte also didn't work out.