OpenEuphoria

Re: goto...

• Posted by Mark Brown <mabrown at SENET.COM.AU> Feb 12, 2002
• 811 views

Hi Karl,

I hope Rob can give us a solution for this.

I am strongly considering buying the source (curiosity....don't actually
think
I am up to doing anything with it!) but it doesn't seem worthwhile if I
can't bind/translate my code if it uses extensions.

I hope Rob can find his way to providing us with a binding/translating
solution which allows registered owners of Eu (perhaps if they have
purchased the whole suite) to create exe's with extensions and still
protect his business plan. Perhaps somewhere in the binding / translating
process a password might stop unregistered users from creating
exe's. Password held in an include? Maybe this is reason enough for
a better installer?

Mark


----- Original Message -----
From: <kbochert at ix.netcom.com>
To: "EUforum" <EUforum at topica.com>
Sent: Tuesday, February 12, 2002 5:36 AM
Subject: Re: goto...



Hi Mark Brown, you wrote on 2/11/02 7:47:35 AM:

>
>Hi Karl,
>
>So, your Euphoria would be the PD core + your extras?
>
>This will be very frustrating if we get wothwhile features but
>can't bind or translate.


It seems to me that it is in
RDS's interest to support these features for Euphoria
extensions, provided you BUY his binder and translator.
Also in this category are tracing and profiling.

I made a brief test to see if I could bind one of my programs
and it insisted on binding with RDS's interpreter. Apparently
bind.exe checksums the exw.exe file that it uses to
prevent binding with extensions.

I therefore would not hold out any hope for translating,
profiling or tracing either.

Sort of cripples any Euphoria extensions, doesn't it.

Karl