*BSD News Article 14747


Return to BSD News archive

Xref: sserve comp.os.os2.programmer:10970 comp.os.coherent:8958 comp.os.linux:35084 comp.os.mach:2731 comp.os.minix:21856 comp.periphs:3495 comp.unix.bsd:11856 comp.unix.pc-clone.32bit:2395 comp.os.386bsd.development:488
Newsgroups: comp.os.os2.programmer,comp.os.coherent,comp.os.linux,comp.os.mach,comp.os.minix,comp.periphs,comp.unix.bsd,comp.unix.pc-clone.32bit,comp.os.386bsd.development
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!bogus.sura.net!news-feed-1.peachnet.edu!umn.edu!csus.edu!netcom.com!jmonroy
From: jmonroy@netcom.com (Jesus Monroy Jr)
Subject: Re: Flowchart symbols (in ASCII) ISO-1028 [BACK AT YA]
Message-ID: <jmonroyC5rz4p.L7B@netcom.com>
Organization: NETCOM On-line Communication Services (408 241-9760 guest)
X-Newsreader: TIN [version 1.1 PL6]
References: <jmonroyC5pxx0.Axv@netcom.com>
Date: Tue, 20 Apr 1993 09:17:12 GMT
Lines: 209


 
 
                Back at ya!
                Back At Ya!
                BACK At YA!
 
 
>> =========================================================================
>> From: peter@NeoSoft.com (Peter da Silva)
>> Subject: Re: Flowchart symbols (in ASCII) ISO-1028
>> Organization: NeoSoft Communications Services -- (713) 684-5900
>> Date: Mon, 19 Apr 1993 11:54:07 GMT
>>
>> In article <jmonroyC5pxx0.Axv@netcom.com> jmonroy@netcom.com (Jesus Monroy Jr) writes:
>> >         The following are symbols I will be using in the
>> >         flowcharts for the FDC and QIC implementations.
>>
>> Why flowcharts? I thought they went out with lovebeads and bellbottoms.
>>
        Why? Do you miss them?
 
>> ==========================================================================
>> From: "Brian E. Gallew" <geek+@CMU.EDU>
>> Subject: Re: Flowchart symbols (in ASCII) ISO-1028
>> Date: Mon, 19 Apr 1993 13:33:46 -0400
>> Organization: Administrative Computing & Info Services, Carnegie Mellon, Pittsburgh, PA
>>
>> Speaking of flowcharts, does anybody know of any packages (PD or
>> commercial) which will read in a C program and generate a flowchart
>> from it?  (We need to understand/document some old code.)
>>
        There are some commercial packages...
        look in the back of PC-Mag or maybe Dr. Dobbs.
 
 
>> ==========================================================================
>> From: terry@cs.weber.edu (A Wizard of Earth C)
>> Subject: Re: Flowchart symbols (in ASCII) ISO-1028
>> Organization: Weber State University  (Ogden, UT)
>> Date: Mon, 19 Apr 93 17:11:35 GMT
>>
>> In article <C5qBq9.5D8@sugar.neosoft.com> peter@NeoSoft.com (Peter da Silva) writes:
>> >In article <jmonroyC5pxx0.Axv@netcom.com> jmonroy@netcom.com (Jesus Monroy Jr) writes:
>> >>         The following are symbols I will be using in the
>> >>         flowcharts for the FDC and QIC implementations.
>> >
>> >Why flowcharts? I thought they went out with lovebeads and bellbottoms.
>>
>> Apparently, there is code to release; everyone knows you flowchart after
>> you program
>>
        Sorry flowcharted before.
 
 
>> and because it is a course requirement, not because the things
>> are useful compared to real engineering tools like structure diagrams,
>> state transition tables,  operation precedence lists, simulation models, and
>> the resulting profiling data.
>>
        This was a run-on sentence. Brought to you by the letters A and B.
 
        Sometime you almost sound professional.
 
>> I'd be happier with meaningful function names
>> and the output of cxref (which I can run myself, thank you).
>>
        If you want to see code... then volunteer as a beta-tester.
 
>> The two places I have seen flow charts in the real world were to sell IBM
>> flowcharting forms (like printer spacing charts, except they couldn't
>> serve a useful purpose in a second life as 1:1.5 scale graph paper) and in
>> the museum of science and industry.
>>
        Don't get around much. Huh?
 
 
>> ==========================================================================
>> From: plph@engin.umich.edu (Mark Montague)
>> Subject: Re: Flowchart symbols (in ASCII) ISO-1028
>> Date: 19 Apr 1993 20:14:25 GMT
>> Organization: University of Michigan Engineering, Ann Arbor
>>
>> In article <1993Apr19.171135.19105@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>> >
>> >The two places I have seen flow charts in the real world were to sell IBM
>> >flowcharting forms (like printer spacing charts, except they couldn't
>> >serve a useful purpose in a second life as 1:1.5 scale graph paper) and in
>> >the museum of science and industry.
>> >
>> >
>> >                   Terry Lambert
>> >                   terry@icarus.weber.edu
>>
>> There *is* a use for flowcharts:  I have found that non-programmers
>> (lawyers, managers, etc...) can read understand them much better than
>> pseudo-code, state machines, and transition diagrams.  They look pretty,
>> and they're graphical, so they don't scare the people who wear business
>> suits.
>>
        Amen, even I have to make money now and then.
 
>> I use flowcharts when I want to make a non-programmer understand a
>> algorithm.
>>
        Like some people we know.
 
 
>> ==========================================================================
>> From: haley@scws4.harvard.edu (Elizabeth Haley)
>> Subject: Re: Flowchart symbols (in ASCII) ISO-1028
>> Date: 19 Apr 93 23:13:55 GMT
>>
>> peter@NeoSoft.com (Peter da Silva) writes:
>>
>> >In article <jmonroyC5pxx0.Axv@netcom.com> jmonroy@netcom.com (Jesus Monroy Jr) writes:
>> >>         The following are symbols I will be using in the
>> >>         flowcharts for the FDC and QIC implementations.
>>
>> >Why flowcharts? I thought they went out with lovebeads and bellbottoms.
>>
>> Actually, while they aren't taught any more, I have found them quite
>> useful, especially in situations where the logic needs to be analyzed
>> often...
>>
        I guess what some of the others are saying is:
        "This thing is borken, so we must fixz it."
 
>> It can also allow you to plan more easily where dividing
>> lines between major sets of subroutines really should fall... Thus
>> allowing for very clean modules and headers, as well as dividing up
>> the labor between people...
>>
>> Besides, it's fun to play with those little template thingys and make
>> all the neat shapes...
>>
        Yes, I agree.  I made a house the other day... had 5 rooms.
 
 
>> ==========================================================================
>> From: kcowin@panix.com (Ken Cowin)
>> Subject: Re: Flowchart symbols (in ASCII) ISO-1028
>> Organization: PANIX Public Access Unix, NYC
>> Date: Tue, 20 Apr 1993 01:20:45 GMT
>>
>> While on the subject of FLOWCHARTS... Are there any UNIX public access
>> type programs like the Windows software "ABC Flowcharter" or "Visio"? I
>> did an Archie to no avail.
>>
>> Ken Cowin
>>
        Sorry Ken, I guess they are not kosher and you may have to
        resort to my primitive work.
 
 
        Sorry!  ^   ^
                  o
                 ___
                /   \
 
 
>> ==========================================================================
>> From: jdb@erato.iowa-city.ia.us (John D. Boggs)
>> Subject: Re: Flowchart symbols (in ASCII) ISO-1028
>> Date: Mon, 19 Apr 93 23:15:35 CDT
>>
>> From article <C5qBq9.5D8@sugar.neosoft.com>, by peter@NeoSoft.com (Peter da Silva):
>> > In article <jmonroyC5pxx0.Axv@netcom.com> jmonroy@netcom.com (Jesus Monroy Jr) writes:
>> >>         The following are symbols I will be using in the
>> >>         flowcharts for the FDC and QIC implementations.
>> >
>> > Why flowcharts? I thought they went out with lovebeads and bellbottoms.
>>
>> Actually, no.  We used them all the time in my systems analysis course last
>> semester.
>>
>> -John D. Boggs     jdb@erato.iowa-city.ia.us
>>                    or    ...!uunet!erato!jdb
>>
 
        You know John some people have no appreciation for the
        finer things in life.
 
>> ==========================================================================
>>
>>
 
        OK, all BS aside, now.
 
                In this medium I have very few and limited ways to
        communicate with the people I am working with.  There are
        at least 2 other OS groups that want a QIC-40/80 driver.
 
                We plan to work together and share Ideas and more.
        I don't have time for silly pranks like this. If you beleive
        that you may have more _or_ better tools for me to work with,
        I will listen.
 
                You want a QIC-40/80 drive?  Either put up with me,
        or write your own.  I don't care, I don't have time for your
        silly attitudes or mediocre premises.
 
                Thank you for your attention.
 
___________________________________________________________________________
Jesus Monroy Jr                                          jmonroy@netcom.com
/386BSD/device-drivers /fd /qic /clock /documentation
___________________________________________________________________________