coq-club AT inria.fr
Subject: The Coq mailing list
List archive
- From: Lionel Elie Mamane <lionel AT mamane.lu>
- To: roconnor AT theorem.ca
- Cc: Coq Club <coq-club AT pauillac.inria.fr>
- Subject: Re: [Coq-Club]Unexpected behavour of Opaque
- Date: Fri, 17 Mar 2006 22:56:34 +0100
- List-archive: <http://pauillac.inria.fr/pipermail/coq-club/>
On Fri, Mar 17, 2006 at 10:41:27AM -0500,
roconnor AT theorem.ca
wrote:
> Why is it that when you declare something as Opaque in a module, it become
> transparent when the module is imported. For example
> (* File: foo.v *)
> Definition X := nat.
(...)
> Opaque X.
Well, it is the documented behaviour.
At section or module closing, a constant recovers the status it got
at the time of its definition.
I suppose that the "Opaque/Transparent" commands were supposed to be
mainly tactic hints, and not actually change the status of the defined
object.
--
Lionel
- [Coq-Club]Unexpected behavour of Opaque, roconnor
- Re: [Coq-Club]Unexpected behavour of Opaque, Lionel Elie Mamane
Archive powered by MhonArc 2.6.16.