You (slang for procreative male appendage) - I was having a "save the world" moment - and now you've robbed me of it:-)

You UK types are toooo dry. Always taking advantage. Now I know what it feels like to be Welsh!:-)

>Terry
>
>Thanks for all the detailed info but, sorry, I'm afraid my post was tongue-in-cheek. Of course I know what flow-charts are - how could I not know when working in IT? (and since 1979 I should add). I even had one of those plastic f/c templates.
>
>My post (accompanied by an emoticon) was to the effect that the use of f/cs is ancient, antiquated, can be confusing, and dates back to the days of in-line, monolithic code (with gotos etc. and no structure). I haven't used a f/c since c. 1980 and everything that can be represented thus can better be done with structure diagrams (e.g. JSP) and pseudocode and Data flow diags (deMarco).
>
>Sorry. I hope someone else gleaned something from your informative discourse.
>
>Terry
>
>
>>>What ARE flowcharts, by the way? I think in the Australian Aborigines' Legends of the "Dream Time People" they were mentioned, but that was eons ago! Nowadays, surely, structure diagrams, Data flow diags, etc.? :-)
>>>
>>>>It's been suggested to reduce the number of bugs in our product that developers should write pseudocode and flowcharts. I did this in high school and some in college but never in a real programming job. Does anyone know if this reduces bugs or this is something that we should have been doing all along?
>>>>
>>>>Thanks