<feed xmlns='http://www.w3.org/2005/Atom'>
<title>coq/contrib/interface/coqparser.ml, branch master</title>
<subtitle>The formal proof system</subtitle>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/coq/'/>
<entry>
<title>Directory 'contrib' renamed into 'plugins', to end confusion with archive of user contribs</title>
<updated>2009-03-20T01:22:58+00:00</updated>
<author>
<name>letouzey</name>
</author>
<published>2009-03-20T01:22:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/coq/commit/?id=7d220f8b61649646692983872626d6a8042446a9'/>
<id>7d220f8b61649646692983872626d6a8042446a9</id>
<content type='text'>
git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/coq/trunk@11996 85f007b7-540e-0410-9357-904b9bb8a0f7
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/coq/trunk@11996 85f007b7-540e-0410-9357-904b9bb8a0f7
</pre>
</div>
</content>
</entry>
<entry>
<title>coq-interface and coq-parser can be calls to coqtop with adequate code dynlink</title>
<updated>2009-02-20T13:39:46+00:00</updated>
<author>
<name>letouzey</name>
</author>
<published>2009-02-20T13:39:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.0x7felf.com/coq/commit/?id=7529f1422c794837b0beb0066ad5ef79ce798e86'/>
<id>7529f1422c794837b0beb0066ad5ef79ce798e86</id>
<content type='text'>
 From files in contrib/interface, we create (if natdynlink is available) two
 plugins named coqinterface_plugin.{cma,cmxs} and coqparser_plugin.{cma,cmxs}.
 These plugins are loaded respectively by CoqInterface.v and CoqParser.v.
 So coq-interface can be "coqtop -require CoqInterface", and coq-parser can be
 "coqtop -batch -l CoqParser" (this one cannot be compiled into a .vo, otherwise
 a customized toplevel is launched during the compilation). Turing coq-interface
 and coq-parser and their .opt versions into shell scripts allow to spare around
 40 Mb of disk space...

 Nota: at dynlink, parse.ml was conflicting with the module Parse of the ocaml
 runtime, so I renamed it into coqparser.ml

git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/coq/trunk@11940 85f007b7-540e-0410-9357-904b9bb8a0f7
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
 From files in contrib/interface, we create (if natdynlink is available) two
 plugins named coqinterface_plugin.{cma,cmxs} and coqparser_plugin.{cma,cmxs}.
 These plugins are loaded respectively by CoqInterface.v and CoqParser.v.
 So coq-interface can be "coqtop -require CoqInterface", and coq-parser can be
 "coqtop -batch -l CoqParser" (this one cannot be compiled into a .vo, otherwise
 a customized toplevel is launched during the compilation). Turing coq-interface
 and coq-parser and their .opt versions into shell scripts allow to spare around
 40 Mb of disk space...

 Nota: at dynlink, parse.ml was conflicting with the module Parse of the ocaml
 runtime, so I renamed it into coqparser.ml

git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/coq/trunk@11940 85f007b7-540e-0410-9357-904b9bb8a0f7
</pre>
</div>
</content>
</entry>
</feed>
