1. More Eu Source Questions
G'day all
Rob, thanks for the reply. However, I've got a few more questions.
Will the source code release include "utility" things like binding,
shrouding and scrambling?
Will we be able to recycle the existing Euphoria docco for our own
Eu mutations, rather than recreating the whole lot from scratch?
How will the source release be copyrighted? Do you have a preferred
licencing model in mind?
Warning: <pure_ignorance> ahead!
This may seem a silly question to those who can code in C and C++
(I'm barely past the "Hello World" stage) but I'll ask it anyway:
will the lack of library source code restrict our ability to change
Eu for new (C compatible) native data types, new syntax, etc? What
bits of Eu are actually *in* the library?
</pure_ignorance>
Regards
Tony
2. Re: More Eu Source Questions
Tony Bucholtz writes:
> Will the source code release include "utility" things
> like binding, shrouding and scrambling?
Scrambling is a feature that can't be revealed
to anyone without compromising the security of already-bound
or already-shrouded code. In general, binding and shrouding
are currently features that you pay for, and will likely
remain so in 2.3. You would therefore not get any of the
source code that supports these features, e.g. bind.ex (unscrambled)
or certain portions of the interpreter.
> Will we be able to recycle the existing Euphoria docco for our own
> Eu mutations, rather than recreating the whole lot from scratch?
Yes, as long as you make it clear that you started with our docs
and you changed them.
> How will the source release be copyrighted?
> Do you have a preferred licencing model in mind?
I'm not using an existing licencing model such
as GNU, BSD etc.
You'll be able to do just about anything with
the source except redistribute it or build back in the features that
RDS is currently selling in our Complete Edition.
With a currently supported C compiler, or some
new compiler you port to, you'll be able to enhance our free
Public Domain Edition and distribute and sell your changes
in binary form.
> will the lack of library source code restrict our ability to change
> Eu for new (C compatible) native data types, new syntax, etc?
> What bits of Eu are actually *in* the library?
I'm not sure what you mean.
You will get all the source you need to build
and modify the Public Domain interpreter on Windows, DOS
and Linux. That includes the source to the run-time library
used by both the interpreter and the Translator.
The run-time library contains
subroutines that are called from the main interpreter
loop, and are also called by Euphoria code translated to C,
e.g. printf(), dir(), sin(), ... etc.
I'm only offering the source code package
to registered users of both the interpreter and
the translator. For 2.3 at least, I'm not planning
to release the source to the Translator itself.
Disclaimer: The above statements are my current thinking
on this matter. It is all subject to change before 2.3 is released.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: More Eu Source Questions
On 18 Jul 2001, at 0:47, Robert Craig wrote:
>
> Tony Bucholtz writes:
> > Will the source code release include "utility" things
> > like binding, shrouding and scrambling?
>
> Scrambling is a feature that can't be revealed
> to anyone without compromising the security of already-bound
> or already-shrouded code. In general, binding and shrouding
> are currently features that you pay for, and will likely
> remain so in 2.3. You would therefore not get any of the
> source code that supports these features, e.g. bind.ex (unscrambled)
> or certain portions of the interpreter.
If we add new words to the language, will the shrouding be affected? What if
we got the api to the shrouder/binder,,, no, then we'd have the Complete
Edition,,, but i *have* the complete edition! ummm.. So if we added a new
word, or added to the syntax of an existing word,, my guess is it won't bind
or shroud.. yeas/no ?
<snip>
> > will the lack of library source code restrict our ability to change
> > Eu for new (C compatible) native data types, new syntax, etc?
> > What bits of Eu are actually *in* the library?
>
> I'm not sure what you mean.
> You will get all the source you need to build
> and modify the Public Domain interpreter on Windows, DOS
> and Linux. That includes the source to the run-time library
> used by both the interpreter and the Translator.
> The run-time library contains
> subroutines that are called from the main interpreter
> loop, and are also called by Euphoria code translated to C,
> e.g. printf(), dir(), sin(), ... etc.
> I'm only offering the source code package
> to registered users of both the interpreter and
> the translator. For 2.3 at least, I'm not planning
> to release the source to the Translator itself.
Ummm,, to get the code for the interpreting engine,, we haveto buy the
translator too? Erk! I was hoping to not haveto do that till i made some
money. <sigh> Especially since any code we add would not be to the
registered complete editions, but only to the Public Edition,, which we may
not be useing cause we wanted the features in the Complete Edition..
Kat
4. Re: More Eu Source Questions
Kat writes:
> So if we added a new word, or added to the syntax
> of an existing word,, my guess is it won't bind
> or shroud.. yeas/no ?
The binder is designed to only work with the RDS
PD interpreter. It would not work with someone else's
modified PD interpreter, and they would not be permitted
to make it work (since that's a feature that we would likely
be selling). Shrouding might work with someone's
modified interpreter, if the changes were relatively minor.
> Ummm,, to get the code for the interpreting engine,,
> we haveto buy the translator too?
Yes. If you weren't already registered for the Translator,
you could remove the message and delay from
the run-time library source and thereby
get most of the value of registering the Translator.
Look at it this way: registered Euphoria users will
pay less than other people for the source.
Those Python and Perl people who are
dying to know how Euphoria can be 40x faster, will have
to register Euphoria (interpreter and translator) before
they pay for the source.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
