jftsang <jftsang@[EMAIL PROTECTED]
> writes:
>Having worked with FMSLogo for many years now I have created many
>programs. Unfortunately, the end-users of most of my programs do not
>have a FMSLogo interpreter. Thus, I have been prompted to search the
>possibility of an FMSLogo compiler which produces stand-alone
>executables (even if they are only text-based and in the command
>line).
The restrictions you're likely to encounter are not a lack of graphics,
which
is just as easy to provide in compiled code, but rather a lack of RUN, and
a
restriction of its children IF, REPEAT, etc. to literal instruction lists
in
square brackets. RUN depends on having the power of the Logo translator
available at runtime. This would be problematic for control structures
implemented as library procedures, such as MAP, FOREACH, FILTER, etc.;
they
would either disappear or have to be reinvented as actual primitives, with
the
same restrictions as IF, etc.
Basically, for the full power of Logo, you need a Logo interpreter
included in
the compiled code. So it's just as easy to solve your problem by
providing a
Logo interpreter to your users. (Compilers are still worthwhile to speed
up
the majority of Logo code that doesn't depend on the interpreter to work.)
|
