Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0006201OCamlOCaml generalpublic2013-10-03 14:482014-06-04 22:11
ReporterAshish_Agarwal 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOSOS Version
Product Version4.01.0 
Target Version4.03.0+devFixed in Version 
Summary0006201: printing of types inconsistent with -short-paths
DescriptionWhen the toplevel is started with -short-paths, the style in which a type is printed changes from the first printing of a type to all successive printings.
Steps To Reproduce$ ocaml -short-paths

# #require "biocaml"
# open Biocaml

# Fastq.in_channel_to_item_stream;;
- : ?buffer_size:int ->
    ?filename:string ->
    in_channel ->
    (Fastq.item, [> Fastq.Error.parsing ]) Core_kernel.Std_kernel._result
    Stream.t
= <fun>

# Fastq.in_channel_to_item_stream;;
- : ?buffer_size:int ->
    ?filename:string ->
    in_channel ->
    (Biocaml_fastq.item, [> Fastq.Error.parsing ])
    Core_kernel.Std_kernel._result Stream.t
= <fun>

The first time we get Fastq.item and the second time we get Biocaml_fastq.item. The latter style then remains for all subsequent invocations. It is not necessary to call the same function both times. The style changes permanently regardless of what value is being executed.

Maybe of relevance: the Biocaml module is a manual pack, i.e. it contains definitions like `module Fastq = Biocaml_fastq". I do not see the above behavior in Core, which uses -pack.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2013-10-03 14:48 Ashish_Agarwal New Issue
2014-06-04 22:11 doligez Status new => acknowledged
2014-06-04 22:11 doligez Target Version => 4.03.0+dev


Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker