Re: [DISCUSS] Moving cnd forward

2023-09-19 Thread Antonio
Some comments below On 18/9/23 22:56, Jan Lahoda wrote: On Mon, Sep 18, 2023 at 10:02 PM Antonio wrote: [...] I.e. the breakpoints from cnd.debugger.common2 would be used in "cpplite.debugger", which should resolve the MIME type clashes. AFAIK there used to be two separate debugger implemen

Re: [DISCUSS] Moving cnd forward

2023-09-18 Thread Jan Lahoda
On Mon, Sep 18, 2023 at 10:02 PM Antonio wrote: > Hi, > > Wow, that seems a lot of work to do _on cpplite_ in order to have cnd > integrated. Also it seems to me there're lots of unknowns in the road! > > The blockers I see are: > > -A) If the cpplite.debugger is to be kept "for native image debu

Re: [DISCUSS] Moving cnd forward

2023-09-18 Thread Antonio
Hi, Wow, that seems a lot of work to do _on cpplite_ in order to have cnd integrated. Also it seems to me there're lots of unknowns in the road! The blockers I see are: -A) If the cpplite.debugger is to be kept "for native image debugging" then cpplite.editor MIME registration should also be

Re: [DISCUSS] Moving cnd forward

2023-09-16 Thread Jan Lahoda
Hi Antonio, Great to see progress on CND! First, the mime types in cpplite were intended to automatically "disable" the cpplite functionality when CND is installed. So, these are not intended to be used at the same time. OTOH, it is true cpplite is used a little bit more than anticipated. So, le

[DISCUSS] Moving cnd forward

2023-09-16 Thread Antonio
Hi all, So it seems people is interested in the CND branch for C/C++ development, and we now have three PRs from external contributors [1]. STATUS: As you may know the CND branch has been pruned from the original Oracle donation (due to license restrictions and code provenance issues), and