Skip to Content.
Sympa Menu

coq-club - Re: [Coq-Club] How to disambiguate short names, when absolute name is same as short name?

coq-club AT inria.fr

Subject: The Coq mailing list

List archive

Re: [Coq-Club] How to disambiguate short names, when absolute name is same as short name?


Chronological Thread 
  • From: Jonathan Leivent <jonikelee AT gmail.com>
  • To: coq-club AT inria.fr
  • Subject: Re: [Coq-Club] How to disambiguate short names, when absolute name is same as short name?
  • Date: Tue, 06 Jan 2015 21:08:40 -0500


On 01/06/2015 03:56 PM, Peter LeFanu Lumsdaine wrote:
Normally, to disambiguate between objects with the same short name, one can
refer to them by their absolute names. E.g. if the working directory
contains identically-named library files in different subdirectories,
Dir1/MyMod.vo and Dir2/MyMod.vo, compiled with module names Dir1.MyMod and
Dir2.MyMod, then issuing

Add Rec LoadPath ".".
Require Import MyMod.

might load either, but one can specify which by giving the absolute name: [
Require Import Dir1.MyMod. ] or [ Require Import Dir2.MyMod. ]


But if there is also a MyMod.vo in the working directory itself (compiled
with module name MyMod), then its absolute name is just [ Mymod ], but in [
Require Import MyMod ], Coq still interprets [MyMod ] as an ambiguous short
name, not as an absolute name. In this situation, is there any way to tell
Coq that we want the module with absolute name [ MyMod ], not the modules
from the subdirectories?

I think the "Top." prefix always works for anchoring absolute names: Top.MyMod

-- Jonathan




Archive powered by MHonArc 2.6.18.

Top of Page