public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Kristoffer Lawson <setok@fishpool.com>
To: egcs@cygnus.com
Cc: sourcenav@sources.redhat.com
Subject: Re: Great work
Date: Fri, 21 Jul 2000 11:14:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0007212105510.19085-100000@gfanrend.fishpool.fi> (raw)
In-Reply-To: <Pine.SUN.3.91.1000721102714.9299B-100000@rtl.cygnus.com>

On Fri, 21 Jul 2000, Mo DeJong wrote:

> use our own parser written for Tcl. To be honest, it would
> be better to toss out our Tcl parser and use the one from
> the Tcl core, and since the Tcl core is already part of
> SN, it is just waiting for someone to come along and
> use it :)

Yes these indeed sounds very sensible.
>  
> Tcl is very dynamic, so in general you can not assume that any command
> does anything. You need to make some assumptions otherwise you will
> get nowhere fast. Set should at least know if it is a local var,
> a global var, or a class instance or class common (static) var, but,
> this is not always possible.

Yes, exactly. But I think the suggested model would be quite sufficient
and at least errenous behaviour would not occur (ie. instance variables
or data appearing as global variables). Ie:

- set commands inside curly bracketrs are not handled in any way, unless:

- if they appear inside the command parameter for while, for, foreach,
eval, namespace eval, proc etc. 

It does require more work (as you have to specify each of those
exceptions), but it also means that "set" syntax appearing in unrecognized
situations is not misunderstood.
> 
> > - I seem to be having problems with emacs/Xemacs and the IDE (btw. I think
> > it's great that you have put in extra effort to get emacs to interact with
> > the IDE). When looking up for a symbol with M-. I get the following error:
> > 
> > (1) (error/warning) Error in process filter: (void-variable DisplayableOb)
> 
> The emacs/xemacs stuff is in there for hackers, so if you have any
> problems you will need to fix them on your own. When you do, please
> send us the patches so the next guy will not need to.

OK, if I have time I'll look into that. Meanwhile is there anybody who
might have a clue about that? Using M-. to lookup a symbol is a documented
feature of "using emacs with Source Navigator" so it might be something
small.

OTOH if the in-built editor could do emacs-style indentation I might
be quite tempted to use it (as it *does* integrate nicely with the IDE).
I realize that's a big requirement but possibly something to look at in
the future.

         -     ---------- = = ---------//--+
         |    /     Kristoffer Lawson      |  www.fishpool.fi|.com
         +-> |    setok@fishpool.com       |  - - --+------
             |-- Fishpool Creations Ltd - /         |
             +-------- = - - - = ---------      /~setok/

      reply	other threads:[~2000-07-21 11:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-21 10:18 Kristoffer Lawson
2000-07-21 10:40 ` Mo DeJong
2000-07-21 11:14   ` Kristoffer Lawson [this message]

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=Pine.LNX.4.21.0007212105510.19085-100000@gfanrend.fishpool.fi \
    --to=setok@fishpool.com \
    --cc=egcs@cygnus.com \
    --cc=sourcenav@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).