On Sat, Oct 21, 2023 at 11:11:47PM +0200, Ralf Hemmecke wrote:
> It seems that Qian wants to revive the Storage line.
> If that happens and there is an easy command like
> 
> )set message storage on/off
> 
> then this will have an effect on jFriCAS.
> 
> If you currently say
> 
> )lisp (setf |$printStorageIfTrue| T)
> 
> then you only get
> 
> Storage: 0 (IN) + 0 (EV) + 0 (OT) + 0 (GC) = 0 bytes
> 
> That looked like no information at all.
> 
> When I programmed it I needed a way to reliably extract the output counter
> from the output. So I switch on $printStorageIfTrue every time something is
> sent from the webinterface to FriCAS.
> 
> The Storage line that comes back in the output is actually ignored, but it
> comes with markers and from them the output counter is extracted.
> I cannot extract them from the "Time: " or "Type: " line, since a user might
> have switched that off.

So, you really need additional marker different from existing markers.
(Ab)using Storage line and its markers for different purpose is bad
as Storage line should be under user control.

> 
> In other words,
> 
> (1) jFriCAS relies on the existence of that Storage line (content
>     uniportant)
> (2) jFriCAS cannot currently show such a storage line.
> 
> Both can, of course, be relaxed if there is a separate reliable way to
> extract the step number from the output of FriCAS.

We should add this.

> Note that this is not that easy in the frame of ")set output FORMATTER off",
> i.e. it must be output that is independent of our formatters.

I am not sure what you mean here.  Do you say that the lines
like

)set output FORMATTER off

pose special difficulty?  AFAIK command do not count towards
step number.  Or you mean that you want step number regardless
of set (possibly empty ???) of active formatters?

-- 
                              Waldek Hebisch

-- 
You received this message because you are subscribed to the Google Groups 
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/fricas-devel/ZTUm2KZ4ukKe8aIz%40fricas.org.

Reply via email to