OpenEuphoria

Re: Open source licenses explained

• Posted by Jason Gade <jaygade at yahoo.com> Sep 22, 2006
• 691 views

Ray Smith wrote:
> 
> Bob Thompson wrote:
> 
> > I was referring to the following extracts from LGPL and how they restrict
> > selling bound/shrouded/compiled programmes. I'm off on business now for
> > two weeks so I won't be able to respond.
> > 
> > Let me know if I have it wrong.
> > 
> > Regards,
> > 
> > Bob

((snip))

> I don't see a problem with this Bob.
> Making a derivative of the library - is making a new version of Euphoria - if
> you make a new version of Euphoria you must open source it.
> 
> Making a program that "uses" Euphoria, can stay closed source if you wish.
> 
> Regards,
> 
> Ray Smith
> <a href="http://RaymondSmith.com">http://RaymondSmith.com</a>

The problem is with programs that are bound or shrouded. Bound code contains a
copy of the interpreter therefore falling under the section that he quoted.

It's a legitimate concern.

--
"Any programming problem can be solved by adding a level of indirection."
--anonymous
"Any performance problem can be solved by removing a level of indirection."
--M. Haertel
"Premature optimization is the root of all evil in programming."
--C.A.R. Hoare
j.