Hello Armin, Thanks for pointing that out. I will definitely take a look at the test code of that module first. -Raihan
On Sun, May 23, 2021 at 1:27 PM Carl Friedrich Bolz-Tereick <cfb...@gmx.de> wrote: > Hi Raihan, > > Could you please describe a bit what you are trying to implement? That way > we could give you a bit more targeted advice. > > Cheers, > > Carl Friedrich > > On May 23, 2021 8:22:48 AM GMT+02:00, Armin Rigo <armin.r...@gmail.com> > wrote: >> >> Hi Raihan, >> >> On Sat, 22 May 2021 at 14:40, Raihan Rasheed Apurbo <apurb...@gmail.com> >> wrote: >> >>> Thanks for helping me out. I was actually looking for a generalized >>> solution. The last paragraph of your answer covers that. What I understand >>> from that is, if I want to understand how pypy gc works and if i want to >>> write my own version of GC at first I have to understand all the tests >>> written on rpython/memory. I will now look extensively into that. >>> >>> I have tried to understand some of the test codes earlier but there is a >>> problem that I faced. Suppose gc_test_base.py written in >>> rpython/memory/test not only uses modules written in rpython.memory but >>> also uses modules like llinterp from rpython.rtyper. As I don't know how >>> those modules work how do I figure out their function written in the test >>> codes? Do you have any suggestions for someone who is facing this issue? >>> >> >> Modules from rpython.rtyper.lltypesystem are essential. You need to >> learn about them to the extent that they are used. They have test >> files in "test" subdirectories, like almost every file in PyPy and >> RPython. >> >> Armin >> ------------------------------ >> pypy-dev mailing list >> pypy-dev@python.org >> https://mail.python.org/mailman/listinfo/pypy-dev >> >>
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
