The Coq mailing list

["James Smith" <james.smith AT aleph-one.com>]

-----Original Message-----
From: James Smith 
[mailto:james.smith AT aleph-one.com]
 
Sent: 23 June 2004 15:41
To: 'Sébastien Hinderer'
Subject: RE: [Coq-Club] java & coq

Hi,

if your aim is to provide an application for non-specialist users then you
should ask what your interface provides. If you simply intend to echo the
output of Coq I doubt that a Java interface (or any other, for that matter)
would provide anything over and above, say, Emacs. A better solution may be
to look at Epigram - I know Conor is keen to work on developing an enhanced
interface to Epigram that can be used with graphical interfaces and
Epigram's two dimensional syntax my well be more suited non-specialist
users.

Regards,

Jim


-----Original Message-----
From: 
coq-club-admin AT pauillac.inria.fr
[mailto:coq-club-admin AT pauillac.inria.fr]
 On Behalf Of Sébastien Hinderer
Sent: 23 June 2004 15:11
To: Houda Anoun
Cc: coq-club
Subject: Re: [Coq-Club] java & coq

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.
--------------------------------------------------------
Bug reports: http://coq.inria.fr/bin/coq-bugs
Archives: http://pauillac.inria.fr/pipermail/coq-club
          http://pauillac.inria.fr/bin/wilma/coq-club
Info: http://pauillac.inria.fr/mailman/listinfo/coq-club