Yes, I think that DAP allows us to make the most of limited developer cycles.

Also, I started writing domain objects and serialization code for the DAP protocol messages, but after a few hours, it seemed like generating code from the schema specification might be the more useful approach, especially if LSP uses schemas to describe its messages (I haven't checked). I think that adding support for generating Pike classes to something like QuickTypes might be the best option at the moment.

What sort of problem are you having setting breakpoints? I don't think I've pushed any changes that broke anything... does the process under debug print out any useful information when you tell it to go?

Bill

December 28, 2018 2:56 PM, "Mateusz Krawczuk" <krawczukmat@gmail.com> wrote:

That's convincing. Having a debug adapter would allow to select from multiple debugger clients already available. I'll try and write one according to your suggestions.

After your recent updates to the debugger-concept branch I'm no longer able to set a breakpoint. Can you please review the wiki and ensure the example scenario you described there is relevant to the current state? This would let me move on with the adapter work.