Hi Alexei, My thought was to match each and every portion of API that Parrot would expose to a external party. So, at the moment, I believe that everything in dod.h might not necessarily be external API. So perhaps I should categorize the document in to two sections. I have also mailed the link to the Parrot community, they are yet to comment.
I also see the need to confirm whether the methods used for marking, sweeping, and reclaiming aren't used by any other component etc. at the VM level. For instance, they do have a concept of Arena, which is not a part of the GC, but which is tightly related. Thanks, Senaka On Mon, Apr 7, 2008 at 1:56 AM, Alexei Fedotov <[EMAIL PROTECTED]> wrote: > Good job, Senaka. > > The general perception was that internal and external GC interfaces > were mixed, which maked this document less usable for harmony-gc-5 > project than it could be. For example, sweeping, marking and > reclaiming are internal interfaces while allocation, stack enumeration > (please take a look at vm_enumerate_root_set_all_threads) and gc > invocation are external interfaces. We should pay more attention to > external interfaces for harmony-gc-5 project. > > Thanks. > > > > > > On Sun, Apr 6, 2008 at 8:35 PM, Senaka Fernando <[EMAIL PROTECTED]> > wrote: > > > > Hi all, > > > > I have almost finished comparing the two interfaces of Harmony and > Parrot. > > However, I'm not 100% sure on whether I got everything right, but I > believe > > that most of it is. Therefore, it would be really great if you could > review > > the wiki page and let me know whether it is correct and precise. > > > > Sections marked as TBD are not yet finalized. And, I have omitted some > > instances of where Harmony supports something and Parrot doesn't for > > simplicity. > > > > The wiki page is found at [1] > > > > [1] > http://wiki.apache.org/harmony/gc_comparison/gc_gen_harmony_vs_parrot > > > > Regards, > > Senaka > > > > > > -- > With best regards, > Alexei >
