From: Ian Roxborough <irox@redhat.com>
To: Rodger Hughes <rodger@synchronicity.com>
Cc: sourcenav@sources.redhat.com
Subject: Re: Source Navigator 5.0 and [incr TCL]
Date: Wed, 06 Jun 2001 17:33:00 -0000 [thread overview]
Message-ID: <3B1ECBCE.5C8746EC@redhat.com> (raw)
In-Reply-To: <3B1EC7E4.FFDC8B0E@synchronicity.com>
Yeah, this is a big downer, we only work with Itcl 1.0/2.0 and
not the 3.0 syntax (Yes, this does mean that we can't parser a
big chunk of Source-Navigator).
The required solution is either fix the current Itcl parser
to work with Itcl 3.0 or write a new one (or adapt an existing one).
When will this be done? Well, I was hoping to have an Itcl 3.0
parser by now, I started writing a new parser Tcl/Itcl in PCCTS,
but I've not done anything on it for a while.
Ian.
Rodger Hughes wrote:
>
> Hello Source-Navigator Team.
>
> I've just started playing with SN 5.0 and I can not get it to recognize
> classes, methods etc... in my ITCL source. I've even tried a very
> simple
> itcl source (see below.) I'm running under Window NT 4.0 SP6.
>
> I also tried SN 4.5.2 and get the same results. It ignores the classes,
> treats
> the methods as functions. The only "classes" I can get it to recognize
> are
> tcl namespaces.
>
> Also, if add an inherit foo line to the Timer class I get an error when
> the code
> parses.
>
> >From what I've seen, SN looks really useful.
>
> Second Question: whats the proper way to install 5.0 on windows? The
> binaries (.zip file) doesn't have an installer like 4.5.2 does and there
> aren't
> any instructions.
>
> Thanks
> Rodger Hughes.
>
> --------------------------------------------------------------------------------
> Name: tmp.proj
> tmp.proj Type: unspecified type (application/octet-stream)
> Encoding: base64
>
> --------------------------------------------------------------------------------
>
> package require Itcl
>
> ::itcl::class foo {
> private variable f_up
> private varible f_act
>
> public method fup {} {
> puts $up
> }
> public method fact {} {
> puts $act
> }
> constructor {up act} {
> set f_up $up
> set f_act $act
> }
> }
> ::itcl::class Timer {
> #inherit foo
> private variable t_up
> private varible t_act
>
> public method up {} {
> puts $up
> }
> public method act {} {
> puts $act
> }
> constructor {up act} {
> set t_up $up
> set t_act $act
> }
> }
next prev parent reply other threads:[~2001-06-06 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 17:16 Rodger Hughes
2001-06-06 17:33 ` Ian Roxborough [this message]
2001-06-06 17:50 ` Mo DeJong
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=3B1ECBCE.5C8746EC@redhat.com \
--to=irox@redhat.com \
--cc=rodger@synchronicity.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).