Uncaught exceptions & packing

[vicuna]

Original bug ID: 5995
Reporter: @Chris00
Assigned to: @alainfrisch
Status: closed (set by @xavierleroy on 2017-02-16T14:18:15Z)
Resolution: fixed
Priority: low
Severity: minor
Platform: x86_64
OS: Debian/Linux
OS Version: 3.9.0
Version: 4.00.1
Target version: 4.03.0+dev / +beta1
Fixed in version: 4.03.0+dev / +beta1
Category: ~DO NOT USE (was: OCaml general)
Related to: #6506
Monitored by: @hcarty

Bug description

When packing a module B into a module A, the exceptions, say E, declared in B must be of course accessed as A.B.E. However, when the exception is uncaught, what is printed on screen is B.E instead of A.B.E which may be confusing...

[vicuna]

Comment author: @lefessan

I can confirm the issue is present with native code.

The problem is that, since -for-pack is optional with bytecode, fixing this issue would introduce a difference between the execution in bytecode and native code.

Maybe it should be fixed both for bytecode and native code when -for-pack is provided.

[vicuna]

Comment author: @damiendoligez

We should definitely fix it for both when -for-pack is provided, then remove the sentence in the documentation that makes -for-pack optional for bytecode.

[vicuna]

Comment author: @alainfrisch

Commit a24e4ed: fix the naming of exception when compiling with -for-pack.

[vicuna]

Comment author: @alainfrisch

Commit a9854a4: document -for-pack as mandatory for ocamlc.