RE: [cdt-debug-dev] Implement snippet editor - How To

[Douglas Schaefer <dschaefe@xxxxxxxxxx>]

cdt-debug-dev-admin@xxxxxxxxxxx wrote on 12/07/2004 09:41:03 AM:

> >-----Original Message-----
> >From: cdt-debug-dev-admin@xxxxxxxxxxx 
> >[mailto:cdt-debug-dev-admin@xxxxxxxxxxx] On Behalf Of 
> >Venkataramana_Jaladurgam
> >Sent: December 7, 2004 7:18 AM
> >To: 'cdt-debug-dev@xxxxxxxxxxx'
> >Subject: [cdt-debug-dev] Implement snippet editor - How To
> >
> >I would like to implement a snippet editor (like the one 
> >available in JDT) in CDT. The user must be able to write 
> >statements of code while debugging is in progress and should 
> >be able to execute them. The results of the execution should 
> >be carried over to main program.
> >
> >Any ideas of how to proceed with it. Ideas a highly appreciated.
> 
> The problem I see with this, is that for my needs > 90% of
> the time you can't compile and run locally, you need to do
> it on some remote target. 
> 
> For a totally generic solution, I think that your best bet
> would be to use a C scripting type language, something like
> http://csl.sourceforge.net/ that would let you interpret the
> C rather than compiling it and executing it.
> 
> Of course, this comes with its own set of benefits and drawbacks,
> but would likely be more general. 
> 
> Once we get a "remote system definition" it will fill that gap
> that ISV's currently fill between building a binary and knowing
> where/how to launch it for execution (potentially under the control
> of the debugger).
> 

Alain brought up an interesting concept at the DOM review yesterday. If 
things work out as planned, the DOM should be able to provide enough 
information to build a C/C++ interpreter. You'd need to build a virtual 
machine but it is possible. Mind you it could be a ton of work, but it was 
a cool idea.

Doug