Results 69 issues of Atila Neves

``` dstep -include /usr/include/linux/stddef.h -I/usr/include/ruby-2.1.0 -I/usr/include/ruby-2.1.0/x86_64-linux -I/usr/include/linux -I/usr/lib/clang/3.4/include/ /usr/include/ruby-2.1.0/ruby.h dstep.core.Exceptions.DStepException@dstep/core/Exceptions.d(13): An unknown error occurred ---------------- dstep(void dstep.driver.Application.Application.run()+0x102) [0x54fa42] dstep(int dstack.application.Application.Application.debugStart()+0x17) [0x54e50f] dstep(int dstack.application.Application.Application._start()+0x15) [0x54e47d] dstep(int dstack.application.Application.Application.start!(dstep.driver.Application.Application).start(immutable(char)[][])+0x41) [0x54e5f9] dstep(_Dmain+0x4f) [0x51266f] dstep(void...

Reviews definitely required here. I thought it through and I *think* this is memory safe. I tried to do nasty things with `-preview=dip1000` and the compiler prevented me, so that's...

Needs Work
stalled
Vision

The resulting build.ninja file has a rule to build a postbuild.exe file.

bug
windows

This ninja rule should do it: ``` libtool --mode=link --tag=CC cc -o $out $in ```

enhancement

e.g. ` ERROR: Could not get info for configuration win64: Could not resolve configuration for package foo`

So that if unit-threaded is generating the file for the unit tests, adding a new file does not cause the main file to be updated.

Originally reported in #207 . The UINT32_C macro doesn't get emitted in the .tmp file, and in fact hardly any cursors are seen at all.