some suggestions
12.10.2000 11:38:04
Hi there!
Just some questions/comments/suggestions concerning the Euphoria to C
translator:
1. Why an Euphoria to C translator and no "real" compiler ? ( or maybe Euphoria
to nasm ?!? )
2. What about droping all system-dependant stuff from the translator and
generate the complete
required (Ansi) C sourcecode, so that the translated program would
compile under any system
with an (Ansi) C compiler ??? ( maybe with some extensions to Euphoria
to link code from other languages ? )
I would love to see my little ( console only ) Euphoria programs run
under BeOS !!!
3. ... or an JIT compiler ??? ( No separate compiling required ! )
A suggestion for Euphoria itself: Euphoria needs CLASSES !!!
that could look like:
<--- snip --->
class CVector
atom x, y, z
procedure CVector() -- the constructor
x = 0
y = 0
z = 0
end procedure
procedure setVector( atom x_, atom y_, atom z_ )
x = x_
y = y_
z = z_
end procedure
procedure scale( atom f )
x *= f
y *= f
z *= f
end procedure
end class
CVector vec
vec.setVector( 1, 2, 3 )
vec.scale( 4.37 )
<--- snip --->
or like in VB ( classes look very much like modules ):
file1:
<--- snip --->
class CVector.e -- like include, reads the file CVector.e
CVector vec
vec.setVector( 1, 2, 3 )
vec.scale( 4.37 )
<--- snip --->
file CVector.e:
<--- snip --->
atom x, y, z
procedure CVector() -- the constructor
x = 0
y = 0
z = 0
end procedure
procedure setVector( atom x_, atom y_, atom z_ )
x = x_
y = y_
z = z_
end procedure
procedure scale( atom f )
x *= f
y *= f
z *= f
end procedure
<--- snip --->
And finally:
Euphoria IS fast! Even if it's interpreted!
Euphoria IS simple! Hope it will not be overloaded with keywords, options, etc.
in future ( except for classes of course! )
Keep it lean!
Euphoria IS kewl! I propably will register !!!
Jareth
|
Not Categorized, Please Help
|
|