| Anonymous | Login | Signup for a new account | 2013-06-18 09:53 CEST | ![]() |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 0004771 | OCaml | OCaml general | public | 2009-04-15 16:21 | 2012-09-17 13:54 | ||||||
| Reporter | dra | ||||||||||
| Assigned To | |||||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||||
| Status | acknowledged | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | 3.11.0 | ||||||||||
| Target Version | 4.00.2+dev | Fixed in Version | |||||||||
| Summary | 0004771: Dynlink.allow_only should call default_available_units or docs should be updated | ||||||||||
| Description | 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.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. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
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 |
| Copyright © 2000 - 2011 MantisBT Group |