Denis Demidov

I can confirm this. `fft`, `fft_benchmark`, `fft_profile` all lead to the internal compiler error when compiled with MS Visual C++ 2013. MSVC 2010 (and I think 2012) manages to compile...

I think I remember one of either g++ or clang++ compiler versions reported a warning about `vexcl/backend/opencl/fft/unrolled_dft.hpp`. Something to the effect that string literals used there are too long according...

The PR #101 did not work for me. VC2013 still crashes on fft.cpp.

Ok, lets say its a Microsoft problem (they should not crash in any case). I would keep it open though to be visible for others.

Visual Studio 2013 still crashes with #114 applied.

`git describe --match ` was there before `exclude`. Would it be possible to use it with a negative regex pattern?

Correction: exclude and match use glob patterns (similar to bash ones), not regexps.

``` git describe --match '[0-9]*' ``` seems to work, although it is not the same as ``` git describe --exclude ev3dev-* ```

How about just creating a subsection in the `Motor` docs, named 'Low level API' and containing native driver commands? This way we keep our current API and let people know...

The following code in motors.rst ```rst Tacho Motor (``Motor``) ~~~~~~~~~~~~~~~~~~~~~~~ .. autoclass:: Motor .. rubric:: Attributes .. autoattribute:: COMMAND_RUN_TO_ABS_POS .. autoattribute:: COMMAND_RUN_TO_REL_POS .. rubric:: Methods .. automethod:: on_for_seconds .. automethod::...