1. Euphoria as a Rapid Deployment language?
I recently had to code this function in C that, well,
pulled the last ounce of strength in me...
It was buggy as hell, because of poor array handling
in C.
I was reallocating chunks of memory, throwing pointers
and byref variables trough the air, etc.
Hard as hell.
I got pissed off at C and decided to implement the
routine in Euphoria, just for the crap of it.
Wha?
It took me 1 minute to code this routine in Euphoria,
and it ran perfectly, just as I expected it to run.
But this did me no good, the code was part of a weird
scripting language, the parser to be exact, and for
speed it can only be coded in C, not Euphoria.
"But wait", I thought, "Can't I just write this one
routine in Euphoria, and the rest in C?".
So that's what I did.
And it works exellent now.
On all three platforms.
But it was hard to interface the Eu code to C...
So what I'm getting at is, Euphoria could be used as a
RAD tool for C programmers that need to implement
dangerous routines more safely.
*IF* a future translator allows better/automatic
Euphoria To C interfacing support.
And offcourse, C is mainly used because of its
portability, so the translator should emit portable
code only, no extra compiled libraries.
I must say I'd pay even 300 dollars as a C programmer
for a tool that lets me code my large and difficult C
routines as small, easy Euphoria routines, and let me
code the more speed sensitive stuff in C.
Mike The Spike
PS. I know that in Linux and Win32 you can call Eu
code from C programs (DLLs) using callbacks, but what
about DOS32 then? And future supported platforms?
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices.
http://auctions.yahoo.com/
____________________________________________________________
T O P I C A -- Learn More. Surf Less.
Newsletters, Tips and Discussions on Topics You Choose.
http://www.topica.com/partner/tag01
2. Re: Euphoria as a Rapid Deployment language?
On 29 Jan 2001, at 15:43, Mike The Spike wrote:
> PS. I know that in Linux and Win32 you can call Eu
> code from C programs (DLLs) using callbacks, but what
> about DOS32 then? And future supported platforms?
<rambling>
If we could easily write device drivers in Eu, that would help some, or use the
redirector
interface in dos, which can be plugged into and out of at any time. How would
this
help? cause the code could be called by any running app written in any language,
and
it becomes a native system call, without re-compiling the OS. Sneakily, you'd
"read"
or "write" to a dos device, rather than a windoze DLL "call". Different
"applications" can
be accessed by using different "directories" in the device, and could maybe even
be
shared across a LAN. Writing TSR's in dos solves many problems that can't be
solved
in a typical program on the plain vanilla dos OS, especially those TSR's linked
into the
timer ints for time-sliced background multitasking.
Once most of my code gets done and modularized, i'd like to port each module to
a
dos tsr, so it is available to all the apps, running as a background process in
dos as
required. I could do intelligent serial port writes, coordinated across
applications,
easily by writing to "Z:\serial.txt", for instance, with the tsr grabbing the
write to that
"file" and processing it properly so all the applications can't interfere with
each other,,
or other stuff.... or whatever, etc.... plug in some new code into the
redirector, and
exec it,, just like dynamic variable execution.....
Kat,
distracted by that $%#^ ball of string again....
____________________________________________________________
T O P I C A -- Learn More. Surf Less.
Newsletters, Tips and Discussions on Topics You Choose.
http://www.topica.com/partner/tag01
