Eoin Ross wrote:
> You have established this its a redistribution in binary form - no
> arguement.
>
> What about this at the end of that statement?
> "in the documentation and/or other materials provided with the
> distribution."
>
> No matter WHAT you send to me (redistribution) ... you are going to
> have to include certain text in some accessable method. A PIC/LED
> flasher can't do it - so you have to provide documentation with it.
>
> The melody card would have to have it somewhere - probably on the
> back with the bar code. If you send the electronics to Hallmark for
> them to use, you provide the documentation to them - and its on them
> to take care of it for their redistribution step.

While this discussion about licenses is interesting in its own right, we
seem to be loosing sight of the original intent.  If I remember right, the
OP created heap routines for a PIC 16.  Most likely nobody would ever use
them even if they were totally free.  Heap routines are of very limited use
on a PIC 16.  So far this requirement hasn't come up in 100 PIC projects,
and I doubt it will come up in the next 100.  In the unexpected event I
would need something like a heap on a PIC 16, it would never occur to me to
look around for someone else's bugware that might implement working heap
routines that might take less time to ensure really work than to write them
from scratch.

Release them any way you want.  Nobody is going to care anyway.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist