1. A Euphoria DLL?
- Posted by Jonas Temple <jktemple at yhti.net> Feb 28, 2002
- 534 views
Since everyone has been talking about wish lists for V2.4, I thought I would throw my 2 cents in. What I would like to see is the ability to create a .dll with the binder. I know that I can get the translator and then compile to make a .dll but that doesn't make any sense to me. Why is this so important that I have broken my silence? For example, if I am creating a system where I am allowing my users to look up a customer number in several different programs wouldn't it be nicer to create a .dll with Eu and then link to that .dll in each program? The alternative is to make the customer lookup a seperate file and include the functionality. Well now when I change the lookup I'll have to re-bind all the programs that used that file. To me, this is the only area where I see the core language needing some improvement. Rob, is this even in the realm of possibility?
2. Re: A Euphoria DLL?
- Posted by petelomax at blueyonder.co.uk Mar 01, 2002
- 468 views
On Fri, 1 Mar 2002 13:17:14 -0500, Matthew Lewis <matthewwalkerlewis at YAHOO.COM> wrote: > > >> -----Original Message----- >> From: Bernie Ryan [mailto:xotron at localnet.com] > >> Matt: >> A bound program is just the executable interpeter with >> a executable program code bound on to the backend of it. >> This would be very different than creating a DLL. > >Different, yes, but how much different? Rather than lumping Eu code to the >normal, executable interpreter, it would be bound to a dll-compiled version. >The bind utility would then adjust the stub to reflect the entry points for >the dll. Again, other than figuring out the proper structure for the entry >points, I don't see why this would be too difficult. :) > >Matt Lewis Drop the "dll" and call it "ell" - a euphoria linked library. The internal structure would be Eu, not C. Obviously no-one wants to bind a bit of euphoria so they can call it from their C program(?). Don't use an existing, probably overcomplex interface, define a new, simpler, & extendible one. The binder needs to be changed to recognise include fred.ell differently to include fred.e, validate the interface details, and ug, load them as needed. Good idea, loads of work, not on my list of priorties though. Pete