Thou shalt have no other gods before the ANSI C standard 1392

a) No two FOOs are exactly the same... *ever* b) Customers get justifiably annoyed when they ask you to build a custom system and you say "well let's start with something I built for somebody else... hang on I've got the tape I snuck out; I'll just kludge it into your system" c) Each progressive FOO will get more refined in some respects. d) I still have my notes on how to build a FOO. Flowcharts even. And even if somebody wanted me to write them an identical FOO on a different system, then (based on the buttumption that I'm familiar with the new target system) I just go back far enough to rewrite^Wredevelop from.

well, duh. what's your point? (I'm not an artist... heck artists aren't artists; they are notorious for reuse).

Do you mean personal utilities and stuff? then my specs already call for it to be portable and I've probably got a vanilla flowchart-pseudocode around somewhere I can use... heck maybe even a template if it's a small enough thingie.

I just answered a post by you where you were complaining about somebody using subroutines and functions.

But as long as you ask, CALLS can be extremely wasteful of machine time if you're in a high-iteration loop. And if you're chunking in a megabyte of generic code when all you need is a specific couple K, then you may have further issues to contend with. YMMV depending on requirements.

rpl