1. RE: Licenses..
Hi Doug,
> 1. What can not be distributed besides the binarys (ex, exw, exu, etc.)?
> Anything? Can I distribute the source files created using Euphoria to C
> translator?
I beleive you can distribute anything that is in the public domain
edition.
> 2. Seeing as there are some processor intensive functions, will I have
> to use the Euporia to C translator to make a library? There will be
> some developers that will not use registered versions of Euphoria and
> will still need the speedier code. And I assume, since I can't
> distribute the Euphoria to C translator, any sort of web interface or
> automatic generation would be bad. :P
The simple answer is write everything in Euphoria and speed up
anything that is to slow.
You might be pleasantly surprised at the execution speed that Euphoria
can achieve.
The translater produces "exe"'s by default.
So if the other developers only need access to your exe's that will
be fine.
If other developers want access to your translated routines inside
Euphoria I think you will need to create DLL's.
I think someone (Matt Lewis?) made "something" to automatically
produce DLL's using the translator??? Have a look through the
Archives at www.RapidEuphoria.com.
I can't see any web interface being developed. The translator is
reasonably priced. If you "need" that functionality it is a small
price to pay.
Regards,
Ray Smith
http://rays-web.com
2. RE: Licenses..
> -----Original Message-----
> From: Ray Smith [mailto:smithr at ix.net.au]
> Hi Doug,
>
> > 1. What can not be distributed besides the binarys (ex,
> exw, exu, etc.)?
> > Anything? Can I distribute the source files created using
> Euphoria to C
> > translator?
The only things you can't distribute are components of the official versions
not included in the PD versions. This includes the binaries, as well as the
bind and shroud utilities. You can distribute source files from the
translator, although IIRC, something translated by the official version
won't compile with the PD run time library. This may be different in 2.3.
I haven't started using it yet. :(
> > 2. Seeing as there are some processor intensive functions,
> will I have
> > to use the Euporia to C translator to make a library? There will be
> > some developers that will not use registered versions of
> Euphoria and
> > will still need the speedier code. And I assume, since I can't
> > distribute the Euphoria to C translator, any sort of web
> interface or
> > automatic generation would be bad. :P
<SNIP>
> If other developers want access to your translated routines inside
> Euphoria I think you will need to create DLL's.
> I think someone (Matt Lewis?) made "something" to automatically
> produce DLL's using the translator??? Have a look through the
> Archives at www.RapidEuphoria.com.
I did, but the translator natively supports building dll's/so's now.
Matt Lewis
