Original bug ID: 4771 Reporter:@dra27 Status: closed (set by @damiendoligez on 2014-07-31T15:27:08Z) Resolution: fixed Priority: normal Severity: minor Version: 3.11.0 Target version: 4.02.0+dev Fixed in version: 4.02.0+dev Category: ~DO NOT USE (was: OCaml general) Monitored by:@glondu
Dynlink.allow_only filters the current list of units available to dynlink'd modules. This is slightly counterintuitive for subsequent calls to allow_only (e.g. in the toplevel) where one might reasonably assume that:
(* Dynlink.loadfile a file and get an exception about module String *)
Dynlink.allow_only ["Pervasives"; "String"];;
meant that Pervasives and String are now both available when in fact only Pervasives will be.
Either allow_only should call default_available_units before filtering or the documentation should be clearer as to how the function behaves.
The text was updated successfully, but these errors were encountered: