From: Jim Ingham <jingham@apple.com>
To: insight@sources.redhat.com
Subject: Re: regenerating tclIndex
Date: Tue, 02 Oct 2001 16:09:00 -0000 [thread overview]
Message-ID: <4E1EC54E-DD23-11D5-A069-000393540DDC@apple.com> (raw)
In-Reply-To: <1006196231.29860.ezmlm@sources.redhat.com>
I am pretty sure that you have to use Itcl to generate tclIndex files
for code that contains Itcl classes, or the classes & methods will not
get included in the index. If you look, Itcl adds its own recognizer to
the mkIndex parser namespace to look for these things. I doubt this
exists in straight Tcl. The indexes might still work if you happen to
hit straight tcl commands that bring all the code you care about in, but
it is not a good bet that it will.
I also have some vague memory that there was a bug in the stock Itcl
index generation code that I fixed in our version, but never got merged
back to the Itcl source base? This may be brain-noise, however.
Jim
On Monday, November 19, 2001, at 10:57 AM, insight-digest-
help@sources.redhat.com wrote:
> Doh. My bad? Didn't we decide that we would just require developers to
> have tclsh8.3?
>
>
--
Jim Ingham jingham@apple.com
Developer Tools - gdb
Apple Computer
WARNING: multiple messages have this Message-ID
From: Jim Ingham <jingham@apple.com>
To: insight@sources.redhat.com
Subject: Re: regenerating tclIndex
Date: Mon, 19 Nov 2001 11:26:00 -0000 [thread overview]
Message-ID: <4E1EC54E-DD23-11D5-A069-000393540DDC@apple.com> (raw)
Message-ID: <20011119112600.8ZGFam1T9csy5vhVPACMBBXc5P5YoA_3-JOfq-pY0ZY@z> (raw)
In-Reply-To: <1006196231.29860.ezmlm@sources.redhat.com>
I am pretty sure that you have to use Itcl to generate tclIndex files
for code that contains Itcl classes, or the classes & methods will not
get included in the index. If you look, Itcl adds its own recognizer to
the mkIndex parser namespace to look for these things. I doubt this
exists in straight Tcl. The indexes might still work if you happen to
hit straight tcl commands that bring all the code you care about in, but
it is not a good bet that it will.
I also have some vague memory that there was a bug in the stock Itcl
index generation code that I fixed in our version, but never got merged
back to the Itcl source base? This may be brain-noise, however.
Jim
On Monday, November 19, 2001, at 10:57 AM, insight-digest-
help@sources.redhat.com wrote:
> Doh. My bad? Didn't we decide that we would just require developers to
> have tclsh8.3?
>
>
--
Jim Ingham jingham@apple.com
Developer Tools - gdb
Apple Computer
next parent reply other threads:[~2001-11-19 19:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1006196231.29860.ezmlm@sources.redhat.com>
2001-10-02 16:09 ` Jim Ingham [this message]
2001-11-19 11:26 ` Jim Ingham
2001-10-02 14:55 Syd Polk
2001-10-02 14:55 ` Tom Tromey
2001-10-02 15:51 ` Keith Seitz
2001-10-03 9:39 ` Tom Tromey
2001-11-19 12:25 ` Tom Tromey
2001-11-19 8:46 ` Keith Seitz
2001-11-18 22:36 ` Tom Tromey
2001-11-18 21:32 ` Syd Polk
-- strict thread matches above, loose matches on Subject: below --
2001-10-02 14:41 Tom Tromey
2001-11-18 18:02 ` Tom Tromey
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=4E1EC54E-DD23-11D5-A069-000393540DDC@apple.com \
--to=jingham@apple.com \
--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).