The patch deals with the beginning stage, transferring data
from fricas to view2/3D, that code deals with the ending stage,
writing data from view2/3D to disk.
Also the problem raised by "THEMOS" is mitigated by the "Fix" part.
But!!! The mitigation was invalided by my "OBEY"->"|run_program|"
Maybe this comment is connected to the sleep stuff...
https://github.com/fricas/fricas/blob/master/src/hyper/htinp.c#L351
==
THEMOS says: There is a problem here in that we issue the (|close|) and
then go on. If this is the last command, we will soon send a SIGTERM and
the whole
On Fri, Apr 19, 2024 at 09:02:59PM +0800, Qian Yun wrote:
>
>
> On 4/19/24 20:41, Waldek Hebisch wrote:
> >
> > Long ago I looked at communication protocol between various
> > processes that we use and my conclusion was that it is
> > inherently racy: there are parallel chanels of communication
On 4/19/24 20:41, Waldek Hebisch wrote:
Long ago I looked at communication protocol between various
processes that we use and my conclusion was that it is
inherently racy: there are parallel chanels of communication
and both ends assume that data comes in right order. I added
a little piece
On Fri, Apr 19, 2024 at 07:12:06PM +0800, Qian Yun wrote:
> You can notice a "pause" when you draw a picture like:
>
> (1) -> draw(x,x=1..2)
>Compiling function %C with type DoubleFloat -> DoubleFloat
>Graph data being transmitted to the viewport manager...
>FriCAS2D data being
You can notice a "pause" when you draw a picture like:
(1) -> draw(x,x=1..2)
Compiling function %C with type DoubleFloat -> DoubleFloat
Graph data being transmitted to the viewport manager...
FriCAS2D data being transmitted to the viewport manager...
<<<>>>
(1)
