Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004771OCamlOCaml generalpublic2009-04-15 16:212013-07-29 15:24
Reporterdra 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOSOS Version
Product Version3.11.0 
Target Version4.01.1+devFixed in Version 
Summary0004771: Dynlink.allow_only should call default_available_units or docs should be updated
DescriptionDynlink.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.allow_only ["Pervasives"];;
(* 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.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0008088)
doligez (administrator)
2012-09-17 13:54

Fix the docs.
(0009823)
frisch (developer)
2013-07-22 12:52

It seems that the behavior is different in native code (allow_only calls init() first).

- Issue History
Date Modified Username Field Change
2009-04-15 16:21 dra New Issue
2009-04-29 15:53 doligez Status new => acknowledged
2012-07-11 14:55 doligez Target Version => 4.01.0+dev
2012-07-31 13:36 doligez Target Version 4.01.0+dev => 4.00.1+dev
2012-09-17 13:54 doligez Note Added: 0008088
2012-09-17 13:54 doligez Target Version 4.00.1+dev => 4.00.2+dev
2013-07-09 17:22 doligez Target Version 4.00.2+dev => 4.01.0+dev
2013-07-22 12:52 frisch Note Added: 0009823
2013-07-29 15:24 doligez Target Version 4.01.0+dev => 4.01.1+dev


Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker