[comp.sys.mac.programmer] Should I post Think Class Lib bug reports here?

oster@dewey.soe.berkeley.edu (David Phillip Oster) (12/10/89)

I've been posting bug reports on the Think Class Lib to the macoops
mailing list.  Are there enough people who use TCL, and don't subscribe to
macoops that it is worth posting my bug reports here?

Merging my personal object system with TCL has been a good experience.
I've found lots of bugs in both, and my new system is much more powerful,
learnable, and maintainable than what I had before.  The work is still
going on.

I've been using THINK C's ability to share folders, and hide folders to
work on three programs at once. My work folder contains:
1.) in a folder called (A.Book) is a version of my address book program
modified to use TCL.
2.) in a folder called (Labels) is a new program I'm working on.
3.) in a folder called (Browser) is a class browser I'm working on,
4.) in a folder called Common is source code common to all three.

This allows me to have only one copy of all my personal source code that
is common to all the programs I am working on.

What I want for the browser is a tool to document TCL classes to the point
that I never use the paper manual. Then I can make my own classes true
first class citizens, since they will be documented as well as THINK's
classes.  The browser draws figures similar to those in the TCL manual,
but better. For example, it draws the class heirarchy like the picture on
page 197, but without so much wasted white space, and with the siblings in
alphabetical order. Double click on a class, and you get a window
describing the class, its variables, and methods, similar to the
illustration on page 179.  I've been ignoring the problem of parsing C for
the moment, just providing an editor for these views and data structures.
Comments?

--- David Phillip Oster            --  No, I come from Boston. I just work
Arpa: oster@dewey.soe.berkeley.edu --  in cyberspace.
Uucp: {uwvax,decvax}!ucbvax!oster%dewey.soe.berkeley.edu