coq-club AT inria.fr
Subject: The Coq mailing list
List archive
- From: S�bastien Hinderer <Sebastien.Hinderer AT loria.fr>
- To: Houda Anoun <anoun AT labri.fr>
- Cc: coq-club <Coq-club AT pauillac.inria.fr>
- Subject: Re: [Coq-Club] java & coq
- Date: Wed, 23 Jun 2004 16:10:40 +0200
- List-archive: <http://pauillac.inria.fr/pipermail/coq-club/>
Hello,
One solution I see is to have two processes: one for your interface, the
other for Coq.
The idea is that the coq process is executed by your interface (with th fork
and exec system calls).
The communication is then done using two pipes. One allows the interface to
send datas to Coq on his standard input, the other one is used to fetch
messages sent by Coq on his standard output.
I guess this is the technique use by Emacs and proof-general...
Hope this helps,
Sébastien.
- [Coq-Club] java & coq, Houda Anoun
- Re: [Coq-Club] java & coq, Sébastien Hinderer
- Re: [Coq-Club] java & coq,
Pierre Courtieu
- Re: [Coq-Club] java & coq, anoun
- Re: [Coq-Club] java & coq,
Pierre Courtieu
- Re: [Coq-Club] java & coq, David Aspinall
- <Possible follow-ups>
- RE: [Coq-Club] java & coq, James Smith
- Re: [Coq-Club] java & coq, James Smith
- Re: [Coq-Club] java & coq, Sébastien Hinderer
Archive powered by MhonArc 2.6.16.