ComputerVoltageSources

Hi Mike
here's my opinion...
if it's ALL public domain, simple attribution in a comment line ie:
* LOADALLDACS courtesy of Grant Richter 
is sufficiently courteous.

here are the guidelines i use:
If all you borrow is lines (to save keystrokes) or blocks of variable
names - no attribution 
if what you borrow is a complete software 'device' like a subroutine
or whole function or operation - attribute it to it's creator

the exception is code that the author has restricted in some way, like
a constraint about commercial use. In these cases it is best to make
an effort to contact the author before declaring his/her inherited
code, 'public domain'. It is always safest to 'inherit' the header
with code  and err on the side of caution, thus, the most restrictive
source trumps the others.

Obviously this can get very convoluted fast and i can't claim that i
have any easy answers. After all i had a very public hissy fit when
synthmodules.com restricted my public domain code and i can see why
folks who WANT to restrict the use of their code would be entitled to
a hissy fit if i, by inclusion, put it out under a public domain chevron.

my rule of thumb when restrictions are ineffect , even partially....
always ask the author (and ask for an answer in writing) if your
header will differ from theirs


-doc 

--- In ComputerVoltageSources@yahoogroups.com, "Mike Marsh"
<michaelmarsh@...> wrote:
>
> Thanks to all that replied regarding posting code here.  I will
> probably post at least one program, since it is modular and can be
> easily modified to provide your algorithm for composition.
> 
> One last question: I shamelessly ripped off much of the code from
> existing samples by Brice and Grant (and others, I think).  Is it
> still kosher to post?
> 
> Mike
>