Re: GtkLib
David writes:
> From the rumor mill at www.slashdot.org, I see that GTK is in the
> process of being ported to the BeOS (take a look at www.gtk.org for
> screenshots).
>
> I mention this because:
>
> 1. I'm playing around with Gtk,
> 2. rumor has it that Peuphoria runs on the BeOS, and
This is still a rumor as far as I know, if anyone can confirm it, I would
be very appreciative.
> 3. GtkLib just *might* run under Peuphoria.
This could be questionable. Peu was still extremely buggy last time I
checked. I tried some of the Euphoria benchmarks, and got some weird
results... like negative time for the sequence initializations (which is
just a repeat() in a for loop.. the Peu evaluates the repeat() at compile
time because it is a constant function, so it ends up just assigning a
constant during the loop) and segfaults shortly thereafter.
> GtkLib already runs/limps/crahses-and-burns under Win32 and Linux. The
> possibility of being able run applications on three different operating
> systems is a bit heady.
Wait until you see Neil 2. I've got graphics windows in X with shared
pixmaps and all that jazz, truecolor support and everything you've come to
love (or hate) about Neil. It should run programs unmodified on Linux,
DOS32 and maybe WIN32 (if I ever boot into that horrid operating system
again 
(note: I'm typing this in Windows now, my parents don't have
linux and I doubt they would appreciate me installing it for them, they
even got a little tweaked about moving from windows 95 to 98... sheesh)
> How's progress on Peuphoria going, Pete?
prog-ress? noun. Forward movement toward a goal or accomplishment... Um,
I haven't touched Peu since Eu Linux came out... I'd much rather code in
Euphoria than code Euphoria in C. Rob Craig should be commended for all
the work he's done in making a stable, safe, easy programming language. I
can't wait until he releases an Alpha for Linux, so I can debug without
having to trace through big chunks of code.
I am still interested in writing Euphoria interpreters and compilers. I
think it's great that the EuOS team is involved in one. I have some
thoughts on how to convert Euphoria to native machine code, for a real
compiler, and that the compiler might be able to be written in Euphoria,
making it a just-in-time compiler. Since it would be compiled just before
runtime, it could take advantage of the processor instruction set,
utilizing 3DNow!, MMX, or SIMD instructions which could be great for
sequence manipulations. It could also use callbacks to itself in the
compiled code for doing some of the more difficult things... like
routine_ids or stuff like that. I remember Ralf spoke of moving
loop-invariant code out of loops, one of many optimizations that could be
done for Euphoria code. Other optimizations might be common
subexpressions and strength reduction (changing multiplies by a constant
into adds inside loops)
La, la, la, later,
_______ ______ _______ ______
[ _ \[ _ ][ _ _ ][ _ ]
[/| [_] |[/| [_\][/ | | \][/| [_\]
| ___/ | _] | | | _]
[\| [/] [\| [_/] [\| |/] [\| [_/]
[_____] [______] [_____] [______]
xseal at harborside.com ICQ:13466657
http://www.harborside.com/home/x/xseal/euphoria/
|
Not Categorized, Please Help
|
|
