Re: [Caml-list] Typing unmarshalling without marshalling types

["Jonathan Roewen" <jonathan.roewen@gmail.com>]

> It isn't broken. The need to search the environment for the
> interpreter is mandated by the requirement scripts invoking
> the names of ocaml executables are transparent with respect
> to both:
>
> (a) whether the code is bytecode or native code
> (b) the machine it runs on
>
> Hard coding the location of the interpreter breaks
> requirement (b): it prevents shipping bytecode
> from one machine to another because two people may
> have installed the interpreter in different places
> (indeed may be running different OS!)

Err, what? OCaml already embeds the full path in bytecode (on
unix-like systems). How should this be any different for an ocaml
compiler tool?

As an example: ocamlmktop DOES embed the full path. Also, paths to
things like stdlib dir etc are full paths embedded in the compiler
tools as well (iirc).