coq-club AT inria.fr
Subject: The Coq mailing list
List archive
- From: Pierre Courtieu <Pierre.Courtieu AT univ-orleans.fr>
- To: S�bastien Hinderer <Sebastien.Hinderer AT loria.fr>
- Cc: Houda Anoun <anoun AT labri.fr>, coq-club <Coq-club AT pauillac.inria.fr>
- Subject: Re: [Coq-Club] java & coq
- Date: Wed, 23 Jun 2004 18:00:38 +0200
- List-archive: <http://pauillac.inria.fr/pipermail/coq-club/>
On 23 jun 2004, Sébastien Hinderer wrote:
> 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...
This is also the technique used in Pcoq (which is written in Java by the
way). Can you precise what kind of tool you are realising?
Pierre Courtieu
- [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.