1. Euphoria as a dll?
I remember Alex or someone else asking if Eu could be compiled as a dll. Why
would you want this?
Jeremy
Edmund Burke: "All that is necessary for evil to triumph is for good men to do
nothing."
2. Re: Euphoria as a dll?
Jeremy Peterson wrote:
>
> I remember Alex or someone else asking if Eu could be compiled as a dll. Why
> would you want this?
It depends on how you compiled it, and what sort of an API you exposed. I've
got ooeu compiled into a dll, and able to use it as an embedded scripting
engine. In this case, the reason to have it compiled into a dll is to speed
up the execution of scripts. I've made it so that it is used exactly the
same as simply including the source, except that you include libeu.e instead
of eu.e. Still needs some more testing, which I probabaly won't get to until
next week what with the holiday.
Matt Lewis
3. Re: Euphoria as a dll?
- Posted by Jeremy Peterson <ptl99 at hotmail.com>
Dec 27, 2005
-
Last edited Dec 28, 2005
Matt Lewis wrote:
>
> Jeremy Peterson wrote:
> >
> > I remember Alex or someone else asking if Eu could be compiled as a dll.
> > Why
> > would you want this?
>
> It depends on how you compiled it, and what sort of an API you exposed. I've
> got ooeu compiled into a dll, and able to use it as an embedded scripting
> engine. In this case, the reason to have it compiled into a dll is to speed
> up the execution of scripts. I've made it so that it is used exactly the
> same as simply including the source, except that you include libeu.e instead
> of eu.e. Still needs some more testing, which I probabaly won't get to until
> next week what with the holiday.
>
> Matt Lewis
Are you going to put it on your website to download?
Jeremy
Edmund Burke: "All that is necessary for evil to triumph is for good men to do
nothing."
4. Re: Euphoria as a dll?
Jeremy Peterson wrote:
>
> Matt Lewis wrote:
> >
> > Jeremy Peterson wrote:
> > >
> > > I remember Alex or someone else asking if Eu could be compiled as a dll.
> > > Why
> > > would you want this?
> >
> > I've got ooeu compiled into a dll, and able to use it as an embedded
> > scripting
> > engine. In this case, the reason to have it compiled into a dll is to speed
> > up the execution of scripts. I've made it so that it is used exactly the
> > same as simply including the source, except that you include libeu.e instead
> > of eu.e. Still needs some more testing, which I probabaly won't get to
> > until
> > next week what with the holiday.
> >
>
> Are you going to put it on your website to download?
>
Yes, I think I should be releasing ooeu v1.8.0 tomorrow. There are a lot of
changes, not the least of which is that it's now embeddable into a Euphoria
app.
Matt Lewis
5. Re: Euphoria as a dll?
Matt Lewis wrote:
>
>
> Yes, I think I should be releasing ooeu v1.8.0 tomorrow. There are a lot of
> changes, not the least of which is that it's now embeddable into a Euphoria
> app.
OK, I guess it's tomorrow (here, at least). You can download it at:
http://sourceforge.net/project/showfiles.php?group_id=73684&package_id=150651&release_id=381208
There's a source package and separate platform specific binary packages.
I've submitted it to the user contribution page. There are several neat
improvements. First, you can embed it (either as source or as a dll/so).
There's also pass by reference. The debugger will now allow you to subscript
a sequence. You can also specify return types for member functions.
Here is the change log since the last 'official' release:
v1.8.0 * Pass by reference added as non-RDS compatible feature
* Debugger no longer crashes on app close under Windows
* Debugger uses its own copy of wxEuphoria dll/so
* Debugger will display subscripts
* Fixed preprocessor bugs
* OOEU can now be embedded in other Euphoria applications (see
Embedding)
v1.7.1 * Fixed bug when using constructors of class members
* Procedures that didn't use goto could cause a crash
* Parser recognizes that subscripted sequences are really objects when
considering polymorphism of member functions
* Fixed preprocessing bugs
* Fixed 'sequence of' bugs
* Preprocesses literal arguments to routine_id() to proper routine
decoration
* Functions (and methods) may define a return type, which will be
considered
for polymorphism purposes
