No sarcasm intended. I used to work at a software development firm and we were forced to use c++. Most of the back and forth that I have been observing with the team is around memory leaks and I just wondered if that is due to your development language choice. Hence, my comment. However, if you are using low level languages to get the fastest processing time, then I can see why you are doing what you are doing. I’m just afraid that there may be some low level design flaw leading to all of these leaks. For instance you might consider using messages between different objects to help isolate object disposal, instead of carefully remembering what object has to be disposed in which order. This is difficult to do because of the late binding due to the flexibility of sage.
Sent from my iPhone > On Dec 4, 2018, at 6:54 PM, David Roe <roed.m...@gmail.com> wrote: > > > >> On Tue, Dec 4, 2018 at 9:06 PM <steven.craigh...@gmail.com> wrote: >> Would it be advisable to change the base programming language to one that >> does automatic garbage collection instead of having to check to see if a >> class has been properly disposed like it appears from all of these related >> bugs? > > I can't tell if you're being sarcastic, but I'll just say that the problem > isn't the language. Both Python and Cython have garbage collection. The > issue is that we want to cache things for speed reasons, but also need to > prevent unbounded growth in Sage's memory usage. > David > >> >> Sent from my iPhone >> >> > On Dec 4, 2018, at 12:44 PM, Jeroen Demeyer <j.deme...@ugent.be> wrote: >> > >> >> On 2018-12-04 18:06, Nils Bruin wrote: >> >> Tripledict does that to some extent (with its keys): if one of the key >> >> parts gets deallocated, the weakref callback removes the strong >> >> reference to the value. >> > >> > Yes, but then we potentially end up again in the situation where things >> > are *only* weakly referenced. Currently, you still need a strong reference >> > in a fixed place and ideally we shouldn't. >> > >> > I have a very preliminary idea at #26811 to "fix" this. >> > >> > -- >> > 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. >> >> -- >> 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. > > -- > 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. -- 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.
