On Wednesday, October 23, 2019 at 1:26:46 PM UTC-7, John Cremona wrote: > > > That all looks very complicated. Before I fixed the eclib source code the > previous method did work, namely to flush stdout and stderr from the > c/python wrapper code after calling any library function (in some cases > this is certainly redundant, but in the case of eclib it was very hard for > anyone other than me to know which library functions might spit out some > error or warning message). Somewhere in src/sage/libs/flint are the > wrapper functions which need this. > > Given that fflush is a system call, it probably has quite a serious overhead. When the routine is meant to do I/O anyway, it's a fair price to pay, but just flushing on the odd chance that a warning was generated could very well be quite costly. For a low-level library like flint, that might be too high a price. I think you want to test for performance regression before working around lacking output flushes by flushing always.
-- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/fea85bb2-bcf1-4832-8478-9bf3a14948ef%40googlegroups.com.
