Re: Question on compiling to bytecode

[Erol Akarsu <eakarsu at cmguc dot com>]

Hi Bruce,

Yes, compiling to java source file and producing bytecode is overhead for
servlet-based applications. But, most of the code, I imagine, will be
distributed multi-agent application that need to have much processing power,
here we need best optimized code.

As Per mentioned, bytecode optimization may be not efficient because we may
not see global picture of source code. I have just quickly checked Jscheme
is generating Java source file, jython does also. I think a Scheme compiler
should do. As a result, we will benefit the strength of both functional,
compiled and interpreted environments, that will empower the e-business
software.

Thanks

Erol Akarsu

Bruce Lewis wrote:

> Erol Akarsu <eakarsu@cmguc.com> writes:
>
> > I was exploring the best language/environment to implement very huge
> > software, ebusines-oriented one. I have concluded that Scheme is the
> > best
>
> If handlying a dynamic environment is one of the strengths that made you
> pick Scheme, keep in mind that your end system may end up adding code on
> the fly, i.e. doing compilation at run time.  In that case, speed of
> compilation will matter too.  I would expect compilation to be
> significantly slower if you created intermediate Java code instead of
> compiling directly to bytecode.
>
> Fast compilation has been nice for BRL.  I haven't had to generate
> .class files and worry about complex dependencies.  Restarting the
> servlet engine and letting each page be compiled in memory on the first
> page hit has sufficed.
>
> --
> <brlewis@[(if (brl-related? message)    ; Bruce R. Lewis
>               "users.sourceforge.net"   ; http://brl.codesimply.net/
>               "alum.mit.edu")]>