Re: Free source code diagramming programs [message #48371 is a reply to message #48304] |
Wed, 12 April 2006 07:54   |
Gary L. Scott
Messages: 3 Registered: September 2003
|
Junior Member |
|
|
mitch grunes wrote:
>> Well yeah, but it's a lot of
>> hard work to trace over
>> 3914 lines of useless Usenet post...
>
>
> OK, next time I'll limit the source code to alt.sources, or maybe find
> another free web hoster that lets me store source code files.
>
> Didn't occur to me that some Usenet reading programs make you read
> everything.
>
> As to the Ben Pfaff, who prefered identation, I do that on my own code.
> It's good enough for short programs, if I make no mistakes.
>
> But the next time someone hands you a 20000 or so line legacy program
> developed by 200 people over 30 years, that no one alive understands,
> you may appreciate whatever help you can get. There is a lot of code
> out there like that. The definition of a professional is that you do
> what you are payed to do.
>
> Brooks Moses's idea of coloring indentation stuff to make it more clear
> sounds neat. But a lot of work - I was trying to stay away from
> postscript.
>
On windows, color would be quite easy using an RTF edit box. You can
then output the RTF content to disk. RTF is widely supported as an
import format to most word processors on other platforms and it remains
editable. Postscript is a printer data stream. It shouldn't be used as
a document interchange format. I would think that it would be
desireable for this output to remain editable so that you can import it
into presentations or other documents and tweak it (fonts, spacing, etc).
--
Gary Scott
mailto:garyscott@ev1.net
Fortran Library: http://www.fortranlib.com
Support the Original G95 Project: http://www.g95.org
-OR-
Support the GNU GFortran Project: http://gcc.gnu.org/fortran/index.html
Why are there two? God only knows.
If you want to do the impossible, don't hire an expert because he knows
it can't be done.
-- Henry Ford
|
|
|