flightaware/Tcl-bounties

Clarification on Tcl Pro bounty

Opened this issue · 7 comments

blacksqr commented

The bounty text states that the Tcl Pro debugger must be "accepted into the core."

I've looked at the debugger code and it appears to be pure Tcl. What do you envision must be accepted into the core in order for the bounty conditions to be satisfied?

bovine commented

If any source code changes to the core Tcl language are required for the debugger to integrate with it, then those changes must be accepted by the tcl core team (either as a TIP or a commit).

The debugger itself could potentially be maintained as a separate repo--if so, we'd like to recommend it be accepted into a separate repo on http://core.tcl.tk/

sleutho commented

I assume "working again with Tcl 8.6" also includes the following new commands?

  • coroutine
  • tailcall
  • yield
  • yieldto
  • try
  • throw
  • and the entire oo:: namespace of functionality?
blacksqr commented

The debugger should work with any valid Tcl code.

sleutho commented

Would you guys consider a bounty to get the Tcl Pro debugger working in the form of a Language Server Extension that can be used with IDEs such as VSCode and many others that support the LSP (Language Server Protocol)?

blacksqr commented

I don't know anything about the Language Server Protocol except what I learned in the last ten minutes of googling.

It seems like it would be a pretty ambitious project.

sleutho commented

I think I lumped the LSP in with the VS Code Debug Protocol. It would be great to have incentive out there to get the Tcl Pro debugger working within an IDE.

conej730 commented

I tinkered with this a couple of years ago using the instrumentation code from the pro debugger for a VS code debugger. If anyone wants to pick that up and continue it have at it.
https://github.com/conej730/vscode-tcl-debug