Hi,
On Mon, 31 May 1999, Asger Alstrup Nielsen wrote:
> > Concerning the thought part below, I just reproduced it so that others
> > can comment on it. Personnally, I agree that some message should be
> > returned on success, but there may be some applications which rely on
> > the fact that nothing is returned.
> >
> > So, fellow developpers, any idea?
>
> In order to keep backwards compatibility, we can just introduce a certain
> command that will enable the "error messages" on success.
>
> Greets,
>
> Asger
This would be perfectly ok for me. BTW, since you speak of backward
compatibility, I assume that people have written other lyx clients (apart
from servermonitor.c in the lyx sources). I would like very much to see
the code of some of them so I can improve my code, e.g. when it comes to
error checking, portability or simply cleanness.
Otherwise, I could simply conform to what the lyxserver does now, i.e. not
writing anything in the out pipe if a command that returns no data
succeeds. In this case, I do not fully understand how to check wheter a
command returning no data has succeeded or not. The only way I know of is
using select(2) to watch status changes in .lyxpipe.out, is that right?
If the status has not changed, than lyx hasn't written anything, therefore
no error occurred.
Thanks to everyone for guidance,
Stefano
Stefano Ghirlanda, Zoologiska Institutionen, Stockholms Universitet
Office: D554, Arrheniusv. 14, S-106 91 Stockholm, Sweden
Phone: +46 8 164055, Fax: +46 8 167715, Email: [EMAIL PROTECTED]
Support Free Science, look at: http://rerumnatura.zool.su.se
