Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nom de module = nom d'exception #3829

Closed
vicuna opened this issue Nov 3, 2005 · 4 comments
Closed

Nom de module = nom d'exception #3829

vicuna opened this issue Nov 3, 2005 · 4 comments
Assignees

Comments

@vicuna
Copy link

vicuna commented Nov 3, 2005

Original bug ID: 3829
Reporter: @alainfrisch
Assigned to: @mshinwell
Status: confirmed (set by @alainfrisch on 2017-05-09T14:33:32Z)
Resolution: fixed
Priority: normal
Severity: tweak
Category: typing
Monitored by: mehdi @hcarty

Bug description

Suite à une inspection du code et une discussion avec Xavier...

buzet ~/bug $ cat not_found.ml
let rec f x = 10
buzet ~/bug $ cat a.ml
Not_found.f 5;;
buzet ~/bug $ ocamlopt -c not_found.ml
buzet ~/bug $ ocamlopt -c a.ml
buzet ~/bug $ ocamlopt -o foo a.cmx
a.o: In function camlA__entry': : undefined reference to camlNot_found__f_57'
collect2: ld returned 1 exit status
Error during linking

alors qu'on s'attendrait à un message du genre:

No implementations provided for the following modules:
Not_found referenced from a.cmx

Ça se produit dès que le nom de l'unité est un des noms d'exception
prédéfinis.

-- Alain

@vicuna
Copy link
Author

vicuna commented Feb 17, 2017

Comment author: @damiendoligez

still present in 4.05

@vicuna
Copy link
Author

vicuna commented May 9, 2017

Comment author: @mshinwell

I cannot reproduce this in trunk (rev b0f6e32).

@vicuna
Copy link
Author

vicuna commented May 9, 2017

Comment author: @alainfrisch

Problem still present, with a slightly modified example in not_found.ml:

let rec f x = print_int x; f x

@github-actions
Copy link

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants