Quoting Waldek Hebisch (2021-04-27 20:25:42) > On Tue, Apr 27, 2021 at 10:45:21PM +0200, Ralf Hemmecke wrote: > > Without looking deeper into your snippet... is there a good reason that > > you must first run some stuff in the session, then compile something and > > later continue with your session? > > > > Why can't you do all the compilation first and then run your computations? > > I do not know what Tobias is doing, but rather typical developement > cycle is as follows: > 1) compile your code > 2) run some tests at command line > 3) edit code to hopefully fix bugs > 4) goto 1 > > To speed up this process it is convenient to preserve as much > of testing context as possible, that is reuse test expressions > stored in variables etc. There are workarounds, like storing > tests in input files, but in general bugs like this one > are problematic. Namely, when debugging freshly written code > bugs in libraries or interpeter are very undesirable, us > one would like to concentrate at current task and rely > on correct working of other FriCAS parts.
Yes, that is precisely my workflow and the reason I wanted to at least report this bug. In my case some preprocessing of data takes quite a while, and I want to quickly compile/edit/recompile and work with that preprocessed data. While doing that I came across this issue, which could in principle be avoided by saving the preprocessed data in a Library for faster access. Similar issues happen there, but I haven't been able to get a minimal example for that yet. Best wishes, Tobias -- 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/162001441166.2620768.1748781744779581166%40T440s.
