OpenEuphoria

Re: .il code/file questions

• Posted by Robert Craig <rds at RapidEuphoria.com> Nov 17, 2004
• 650 views

Andy Serpa wrote:
> 1) Can I create (unshrouded) .il files that will run with backend.exe by using
> the
> .il producing code in the PD source?

No. The .il format is proprietary.
I'm trying to make Euphoria as open as possible,
while still having something to sell.
I can't let the whole world edit my source and
produce modified versions of Euphoria, that run at the same
speed as mine.
 
> 2) Can I translate .il files?

No. The owner of the .il can translate his original source.
Anyone else should not be allowed to convert a .il 
into readable C source.
 
> 3) Why not release the Eu source for the translator?
> 
> What I really want to know is if I hack the Eu front-end, is there a way to
> use this
> new front-end as usual with the rest of the Euphoria tools?  (i.e.
> translating, or
> at least binding)  Obviously I can register the interpreter source and create
> a modified
> interpreter.  It seems natural that since the translator uses the same
> front-end now
> that I would also be able to create a modified translator so that I can do all
> the
> things I can usually do, but with a customized version of Eu.
> 
> Because what would really be desirable is to be able to develop programs in my
> modified
> (front-end hacked) version of Euphoria and then be able to distribute an
> executable of
> that program, preferably translated, or at least bound.  In other words, I
> have no interest
> in creating & distributing a modified version of Euphoria, but in creating a
> modified
> version of Euphoria for myself that I can develop programs with.  However, if
> there is
> no way to distribute such developed programs (as executables), then the worth
> of the whole
> thing is much less, at least for me.
> 
> Possible?  Allowed?

In theory, I could sell the translator source, but with
the restriction that it can only be used for private use,
and not for creating and distributing new versions of Euphoria
to the masses. It would involve extra 
configuration/packaging/documenting/tech suport 
work for me, and I don't think there are very many people,
other than potential competitors,
who would have the ability or desire to modify the translator 
in a significant way, though some front-end changes might be easy.
In general, it's quite a bit more complicated than the interpreter.

It provides me with one of my last "fig leaves" in this
age of openness. 

Regards,
   Rob Craig
   Rapid Deployment Software
   http://www.RapidEuphoria.com