From f19a9d9d3a410fda982b2cf9154da5774f9ec84f Mon Sep 17 00:00:00 2001 From: letouzey Date: Fri, 28 Jan 2011 13:20:41 +0000 Subject: Remove the "Boxed" syntaxes and the const_entry_boxed field According to B. Gregoire, this stuff is obsolete. Fine control on when to launch the VM in conversion problems is now provided by VMcast. We were already almost never boxing definitions anymore in stdlib files. "(Un)Boxed Definition foo" will now trigger a parsing error, same with Fixpoint. The option "(Un)Set Boxed Definitions" aren't there anymore, but tolerated (as no-ops), since unknown options raise a warning instead of an error by default. Some more cleaning could be done in the vm. git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/coq/trunk@13806 85f007b7-540e-0410-9357-904b9bb8a0f7 --- kernel/cooking.mli | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'kernel/cooking.mli') diff --git a/kernel/cooking.mli b/kernel/cooking.mli index 0f604a4be..09b42d0b1 100644 --- a/kernel/cooking.mli +++ b/kernel/cooking.mli @@ -24,7 +24,7 @@ type recipe = { val cook_constant : env -> recipe -> constr_substituted option * constant_type * constraints * bool * bool - * bool + (** {6 Utility functions used in module [Discharge]. } *) -- cgit v1.2.3