On Mon, Mar 25, 2013 at 10:24 PM, Daniel King <dank...@ccs.neu.edu> wrote:
>
> To our problem:
>
> - Can someone provide insight as to the pros and cons of compilation (to
> executable)? Do we lose a significant amount of performance by not
> compiling
> (to executable)?
Compilation to executable probably provides roughly the same
performance as not compiling. It's possible that file i/o or file
layout will change this slightly, but no interesting optimization
happens in the "compile to executable" process. It's mostly just a
packaging step -- useful when someone like your professor wants an
executable file.
> - How does compilation to executable compare to byte-code compilation?
The executable will embed the results of byte-code compilation.
> - Any ideas as to avoiding this issue in the first place? Forcing the
> compiler
> to include the necessary dependency?
Add an explicit `require` of the missing dependency in your main file
(the one that you're compiling to an executable), like this:
(require math/private/array/typed-array-indexing)
Sam
____________________
Racket Users list:
http://lists.racket-lang.org/users
