Scott, Thanks very much--very clear and helpful response!
Aside 1: Something I'm going to keep wondering about as I go through the nedit code: would some additional comments (on this point) be of value to anyone beside myself? (And would they even be of value to myself a few years from now when I presumably "know" these kinds of things?) Or, would it be of value to have sort of a commentary on some of the code in separate file(s) dedicated to newbies to C and or the nedit codebase? In this case, maybe a text.c.commentary file, unless the comments are general enough to be worthy of a nedit.commentary file (in both cases, with a shorter extension, like .cmt, or .cmty, or ??)? Aside 2: I guess I should learn to use a debugger with the nedit code--I presume I'd have to have a binary that matched the source code I'm reviewing (i.e., compile from CVS) and do whatever it takes to enable the debugging symbols. Something to work towards (that is, both compiling nedit and setting up a debugger). ;-) (I'll get around to it someday.) Randy Kramer -- "I didn't have time to write a short letter, so I created a video instead."--with apologies to Cicero, et.al. On Monday 18 August 2008 09:37 am, Scott Tringali wrote: --< good stuff snipped >-- -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
