OpenEuphoria

Re: Compiler status

• Posted by Robert Craig <rds at ATTCANADA.NET> Jul 13, 2000
• 552 views

Ben Fosberg writes:
> Is it being claimed here that the Win32 executable for the
> interpreter includes the dos graphics library? If not,
> those of us writing for Win32 aren't being "burdened" with
> the library, are we?

Only the DOS32 interpreter contains the WATCOM
graphics library. That's why pixel-graphics
library routines such as polygon(), ellipse(), pixel() etc.
are currently only supported for DOS32. That's also *part*
of the reason why ex is bigger than exu and exw.
It would be nice to someday support these routines
on Linux and WIN32, but it's not a really high priority
at the moment.

> Despite the fact that we all keep saying "compiler,"
> I believe the gizmo Rob described was a "translator."
> You put in Euphoria and you get out C source,
> which you then feed into a C compiler.

A compiler is a translator from a source language to a lower-level
target language.

A C compiler translates the C language to machine language.

The Euphoria compiler translates Euphoria into C.
The techniques used are very similar to a normal compiler.

I think it's fair to call it a compiler, but to avoid confusion
I will frequently remind people that it translates to C and
that you need a C compiler to complete the job.

Regards,
   Rob Craig
   Rapid Deployment Software
   http://www.RapidEuphoria.com