| Re: Free source code diagramming programs [message #48361 is a reply to message #48304] |
Thu, 13 April 2006 10:27   |
Al Balmer
Messages: 3 Registered: April 2006
|
Junior Member |
|
|
On 13 Apr 2006 10:03:07 -0700, "mitch grunes" <idlwizard-1@yahoo.com>
wrote:
>> Well... my favourite text editor already does what your program do and
>> does it live while I'm editing code...
>
> Are you talking about the EMACS editor?
Many modern program editors do it. Most are easier to learn than emacs
<g>.
> I confess I'm not smart enough
> to learn it well, and when I tried it it did some things I didn't
> expect. I prefer simpler editors that only do predictable things.
> Perhaps it is because I never learned much LISP.
>
> I do remember EMACS did something right - you could make it jump to the
> beginning or end of the current block - at least if you trust the code
> block structure to be correct. When you are fixing that struture in
> someone else's code, you don't want your text editor to be so "smart"
> it won't let you. (Taking again the example of debugging tens of
> thousands of lines of legacy code that doesn't quite work right.)
>
> Pretty printers (auto-indentation, etc.) lose a lot of information,
> when you are trying to fix such,
Could you elaborate on this? What information is lost by reformatting?
> and tend to mess up comments,
> especially when the author carefully lined up the columns of his/her
> comments or code in some sort of table.
That can happen, but some (most?) reformatters can be told to leave
comments alone.
> So I leave the source code
> intact, and create seperate diagrams.
>
> I've written a lot of operational code over the last 25 years that ran
> various places and was sometimes embedded in ship, air and space-borne
> platforms. Sometimes I've had to debug monsters. (Like the pretty lady
> said, professionals do what they are paid to do.
As a professional, I've often considered it my duty to educate those
who tell me what to do ;-)
> Though, at the moment,
> I am between jobs.) I've found these tools useful. But every programmer
> has their own way of working. If you don't like mine, don't use it!
--
Al Balmer
Sun City, AZ
|
|
|
|