Re: More Eu Source Questions
- Posted by Kat <gertie at PELL.NET> Jul 17, 2001
- 383 views
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