public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Paul Schlie <schlie@comcast.net>
To: <insight@sources.redhat.com>
Subject: Re: Current Status of Insight
Date: Sat, 14 May 2005 22:13:00 -0000	[thread overview]
Message-ID: <BEABF056.A26D%schlie@comcast.net> (raw)

>> But what Java does not have - is a command line it is
>> compiled langauge Tcl/Tk - it is some what enherent.
>
> Well, something similar could be implemented in Java with BeanShell
> (http://www.beanshell.org/). jEdit uses this.

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.

(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.)



             reply	other threads:[~2005-05-14 22:13 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-14 22:13 Paul Schlie [this message]
2005-05-16  5:35 ` Steven Johnson
2005-05-16 13:18   ` Insight and Licencing of TCL/TK Code Steven Johnson
2005-05-16 13:31     ` Duane Ellis
2005-05-16 13:39       ` Jon Beniston
2005-05-16 14:15         ` Steven Johnson
2005-05-16 16:12           ` Christopher Faylor
2005-05-17 19:33   ` Current Status of Insight Fernando Nasser
2005-05-16 16:10 ` Christopher Faylor
2005-05-16 17:18   ` Paul Schlie
  -- strict thread matches above, loose matches on Subject: below --
2005-05-17  8:26 Roland Schwingel
2005-05-17 10:18 ` Steven Johnson
2005-05-16 23:45 Paul Schlie
     [not found] <1115992411.3092.ezmlm@sources.redhat.com>
2005-05-13 15:44 ` E. Weddington
2005-05-13 17:15   ` Christopher Faylor
2005-05-13 17:35     ` Bernhard Walle
2005-05-13 17:45       ` Christopher Faylor
2005-05-13 17:58         ` Bernhard Walle
2005-05-13 21:51           ` Fernando Nasser
2005-05-14 14:54             ` Duane Ellis
2005-05-14 17:25               ` Bernhard Walle
2005-05-17 19:38               ` Fernando Nasser
2005-05-13  8:14 Roland Schwingel
2005-05-13  1:15 Paul Schlie
2005-05-12 10:07 Steven Johnson
2005-05-12 10:13 ` Jon Beniston
     [not found]   ` <2636500f05051203276a294e8f@mail.gmail.com>
2005-05-12 10:29     ` Nickolay Kolchin
2005-05-12 15:17 ` Keith Seitz
2005-05-12 21:46   ` Steven Johnson
2005-05-12 22:42     ` Duane Ellis
2005-05-12 22:45     ` Duane Ellis
2005-05-13  2:09     ` Christopher Faylor
2005-05-13  2:19       ` Keith Seitz
2005-05-13 13:53         ` Steven Johnson
2005-05-13 14:05           ` Christopher Faylor
2005-05-13 14:18             ` Jon Beniston
2005-05-13 14:21               ` Christopher Faylor
2005-05-13 14:16           ` Hans W. Horn
2005-05-13 14:29             ` Christopher Faylor
2005-05-13 14:33           ` James Lemke
2005-05-14 11:14           ` Nickolay Kolchin
2005-05-17 12:51             ` Fernando Nasser
2005-05-16 22:07         ` Steven Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BEABF056.A26D%schlie@comcast.net \
    --to=schlie@comcast.net \
    --cc=insight@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).