On 30/08/18 12:00, Henry Vermaak wrote:
On Thu, Aug 30, 2018 at 10:57:21AM +, Mark Morgan Lloyd wrote:> Ah yes, that's it, thanks very
much.> > WriteLn(StdErr, Format('# Socket %s, clock resolution %8.6f uSec',>
[socketName, ts.tv_nsec / 1000]));> ttextrec(StdErr).flushfunc:=
On Thu, Aug 30, 2018 at 10:57:21AM +, Mark Morgan Lloyd wrote:
> Ah yes, that's it, thanks very much.
>
> WriteLn(StdErr, Format('# Socket %s, clock resolution %8.6f uSec',
> [socketName, ts.tv_nsec / 1000]));
> ttextrec(StdErr).flushfunc:= ttextrec(StdErr).inoutfunc;
> while
On 30/08/18 10:15, Henry Vermaak wrote:
On Thu, Aug 30, 2018 at 09:45:00AM +, Mark Morgan Lloyd wrote:> On 30/08/18 09:00, Henry Vermaak wrote:> >On Thu, Aug 30, 2018 at
07:52:54AM +0200, Martin Schreiber wrote:> > >In order to flush textfiles automatically I use> ">
On Thu, Aug 30, 2018 at 09:45:00AM +, Mark Morgan Lloyd wrote:
> On 30/08/18 09:00, Henry Vermaak wrote:
> >On Thu, Aug 30, 2018 at 07:52:54AM +0200, Martin Schreiber wrote:
>
> >In order to flush textfiles automatically I use> ">
> >ttextrec().flushfunc:= ttextrec().inoutfunc;> "> after it
On 30/08/18 09:00, Henry Vermaak wrote:
On Thu, Aug 30, 2018 at 07:52:54AM +0200, Martin Schreiber wrote:
In order to flush textfiles automatically I use> "> ttextrec().flushfunc:=
ttextrec().inoutfunc;> "> after it is opened.
Reading text.inc this morning lead me to believe this is the
On Thu, Aug 30, 2018 at 07:52:54AM +0200, Martin Schreiber wrote:
> On Wednesday 29 August 2018 17:01:54 Mark Morgan Lloyd wrote:
> > I think I've seen this question asked before, my apologies if this was
> > recently.
> >
> > I've got two programs intended to be functionally identical, one in
On Wed, 2018-08-29 at 15:01 +, Mark Morgan Lloyd wrote:
> I've got two programs intended to be functionally identical, one in Perl
> and the other in FPC. They read a unix-domain datagram, decode the
> message, and emit output; if this goes to a file then it's reasonable to
> monitor it
