This is the mail archive of the insight@sources.redhat.com mailing list for the Insight project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Wouldnt a front end to GDB written in Java, and using MI be Eclipse CDT? Surely it would be better to contribute to that project, if thats what people wanted, rather than do it again? The Eclipse CDT GDB Front end certainly seems to need a lot of work, especially where access to the GDB command line, and embedded development are concerned (I cant find how to do a "Load" from the interface, for example). [This is not a criticism of Eclipse/CDT or the work they have already done, which is a lot, just an observation.]But what Java does not have - is a command line it isWell, something similar could be implemented in Java with BeanShell
compiled langauge Tcl/Tk - it is some what enherent.
(http://www.beanshell.org/). jEdit uses this.
I would agree with that.It seems a lot simpler to simply encourage Insight/GDB as it present stands, to be officially (or even semi-officially) considered as part of the GDB release, and maintained as interest allows along side if it; and remain complemented with the separately maintained TK/TCL library etc. as may be necessary in parallel; similar to the way it is now, but without the sigma of "it's dead" lying over it's head.
I would agree with that also.(Although I'm personally not fan of TK/TCL, I seriously doubt any attempted re-architecture would end up being more productive than disruptive; so an in-place successive refinement seems simplest and most logical.)
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |