> On 8/06/2016, at 19:52, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > > On 2016-06-08 00:14, William Stein wrote: >> On Tue, Jun 7, 2016 at 6:12 PM, Francois Bissey >> <francois.bis...@canterbury.ac.nz> wrote: >>> The version from the sage-on-gentoo overlay has been hacked to explicitly >>> write data generated by the user in ~/.sympow. If indeed you make a system >>> wide install where the user cannot write it will certainly fail. >> >> This is indeed exactly why it fails for me (silently from within sage >> and with a segfault from the command line). > > So sympow *segfaults* if it cannot open a file? >
The quality of the code is the biggest reason for removing sympow. It is simply unmaintainable. I was once discussing it with David Kirkby and he told me we couldn’t even put it as a candidate for the obfuscated C contest because it is not actually valid C. François -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
