| Anonymous | Login | Signup for a new account | 2013-06-19 04:39 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 | ||||||
| 0003589 | OCaml | OCaml general | public | 2005-04-12 12:51 | 2005-04-14 16:56 | ||||||
| Reporter | administrator | ||||||||||
| Assigned To | |||||||||||
| Priority | normal | Severity | feature | Reproducibility | always | ||||||
| Status | acknowledged | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | |||||||||||
| Target Version | Fixed in Version | ||||||||||
| Summary | 0003589: ocamldebug should see through abstract interfaces | ||||||||||
| Description | Full_Name: Marc Herbert Version: 3.08.2 OS: linux Submission from: lns-vlq-37-lyo-82-253-121-251.adsl.proxad.net (82.253.121.251) ocamldebug should see through abstract interfaces, it would make it much more useful (I have no idea if this difficult to implement). Assume you have some abstract type like this: mylib.mli: module MyAbstractType = struct type opaque_type val get_string opaque_type -> string end When ocamldebug is stopped inside some module linked to mylib.cmi/cmo, printing opaque_type variables only prints <abstr>, not very useful... One step later you enter MyAbstractType.get_string, and suddenly you can see what's inside opaque_type! | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
Notes |
|
|
(0000255) administrator (administrator) 2005-04-14 16:56 |
wholeheartedly seconded - DD |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2005-11-18 10:13 | administrator | New Issue | |
| Copyright © 2000 - 2011 MantisBT Group |