CTFE Status 2

[H. S. Teoh via Digitalmars-d]

On Mon, May 01, 2017 at 06:23:08PM +0000, Stefan Koch via Digitalmars-d wrote:
> On Sunday, 30 April 2017 at 19:52:27 UTC, H. S. Teoh wrote:
> > On Sun, Apr 30, 2017 at 01:26:09PM +0000, Stefan Koch via Digitalmars-d
> > wrote:
> > > On Thursday, 16 February 2017 at 21:05:51 UTC, Stefan Koch wrote:
> > > > [ ... ]
> > > 
> > > Big news!  The first step to include debug info has been done.
> > > 
> > > Yes this means you will be able to step through ctfe code while
> > > the compiler executes it.
> > 
> > Wow! Will that be accessible to users in the end?  That could be a
> > totally awesome way of debugging CTFE code!
> > 
> > 
> > T
> 
> Yes the plan is to make it accessible for the advanced user.  probably
> with a really bad ui, though (since I am awful at UI code).

I'm not sure about providing a debugger UI inside the compiler itself...
it's certainly possible, and could lead to interesting new ways of using
a compiler, but I was thinking more along the lines of providing the
necessary hooks so that you could attach an external debugger to the
CTFE engine.

But if the debugger UI is simple enough, perhaps having it built into
the compiler may not be a bad thing. It would also avoid potential
trouble caused by some platforms not having debuggers capable of
plugging into the compiler in that way.  But still, I can see people
demanding IDE integration for this eventually... :-O


T

-- 
Obviously, some things aren't very obvious.