Euphoria To C -- I\'m Back!
So I said I was going to return after Euphoria to C translator was released (I'm
a busy...lesbian).
And here I am.
I also said that if the translator was crap, I would release and market U4IA++,
wich includes a translator and interpretter for over 70 compiler, hardware and OS
platforms.
I installed the Translators for both DOS and Windows after messing around with
the incorrect library include paths a bit, and here is what I found of it;
Size
-*-*-
I'ts HUGE!
The executable produced by Watcom is actually even BIGGER than the interpretter!
170kb for a small program containing only a single loop and including graphics.e
and get.e!
And that's not even half of it! 170Kb is the size of the executable ALONE, let's
not talk about the 260Kb DOS4GW required to actually run the executable!
Speed
-*-*-*
It's SLOW!
I wrote a small graphics benchmark program wich consisted out of the following
code;
include get.e
include graphics.e
if graphics_mode(256) then end if
for ix = 1 to 50000 do
pixel(rand(16),{rand(640),rand(400)})
end for
puts(1,"FINISHED!\n")
if wait_key() then end if
and guess what?
The COMPILED version runs 4 times slower than the interpretted one!
This is probably (read: not likely) due to DOS4GW, but a hell of a lot of people
will want to use DOS4GW so it doesn't matter.
Try it.
Translate above code to C and run emake.bat in the Binw directory of Watcom, and
you'll see it runs slow as hell!
I used Watcom v 1.1 to compile the code, BTW.
Readability
-*-*-*-*-*-*
WTF?
The code generated is less than non-readable!
It'll give you a stroke just attempting to make out what is being done!
Usability
-*-*-*-*-*
Wha?
No new features?
And there never will be, unless you figure out a way to speed up the slow
graphics code produced.
Let's not even talk about the shitty restrictions the free edition has...
Verdict
-*-*-*-*
People, people...
What a piece of flying shit!
Be 100% sure I will release, market and publish my personal U4IA++ package
within the next months,
and release a public domain version within a week.
My package outperforms pure and clean ANSI C with a few percent through
conditional Inline ASM, let alone Euphoria, compiled or not.
Hundreds of libraries, thousands, if not millions of lines of documentation
including windows, graphics and console programming, support for the TooL
Playstation II development platform through CodeWarrior, PsyQ-kit based
Playstation MIPS 3000 support using the free GNU C for MIPS, PsyQ-kit based N64
MIPS4000 support with Reality chip specific graphics optimisations, Dreamcast
Windows CE support through Visual C++, etc. ad infinitum, run-time error
checking, crash protection, tracing, DeBug onscreen Joystick controlled tracing
for console platforms, OOP, NightShade (tm) portable machine language,
DLL/OCX creation, ASM to C translation, dynamic interprettation, portable DLL
format, and a crapload of shrink-wrapped freeware and custom C/C++ compilers to
go with everything.
Forget about this home-made slow POS, get your hand on the fastest high-level
programming language in history: U4IA++.
Mike The Spike
PS. I'll be back soon. First a public domain version of U4IA++ will be given to
you alone, as I planned earlier, because you are the only people that know the
Euphoria language and can provide quick feedback when possible bugs are found.
I'm making arrangements as of now to get U4IA++ out t ehe door as soon as
possible. The idea was for me to help out RDS and convince them to start work on
a translator, and if they failed, I would release my own system. They failed.
*********************************************
Want free email? Sign up at http://www.freeze.com !
|
Not Categorized, Please Help
|
|
