Browse thread
Securely loading and running untrusted modules
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Virgile Prevosto <virgile.prevosto@m...> |
| Subject: | Re: [Caml-list] Securely loading and running untrusted modules |
Le 04/05/2005, à 03:17:46 PM, Richard Jones a écrit:
> A much more serious problem which I've just found is that _any_ module
> (even the empty module) seems to require Pervasives. Thus it seems to
> rich@arctor:/tmp$ ocamlc -c test_module.ml
Have you tried with the -nopervasives flag of ocamlc ? [of course this
supposes that your module does not rely on any function of the core
library, which is the case for the empty module]
~ [516]$ ocamlc -nopervasives -c test_module.ml
~ [517]$ ocamlobjinfo test_module.cmo
File test_module.cmo
Unit name: Test_module
Interfaces imported:
f7db4d58568a6e5a2cfe62ef59a52df1 Test_module
Uses unsafe features: no
--
E tutto per oggi, a la prossima volta
Virgile