On 12/21/05, John Cowan <[EMAIL PROTECTED]> wrote:
> felix winkelmann scripsit:
>
> > Once data is in the heap,
> > it is handled in a standard stop-and-copy manner with two semispaces between
> > which data is copied back and forth on every major collection.
>
> So, a classic Baker GC. The troubl
felix winkelmann scripsit:
> Once data is in the heap,
> it is handled in a standard stop-and-copy manner with two semispaces between
> which data is copied back and forth on every major collection.
So, a classic Baker GC. The trouble with those is, of course, that really
long-term data gets cop
On 12/20/05, John Cowan <[EMAIL PROTECTED]> wrote:
> felix winkelmann scripsit:
>
> > The secondary
> > heap follows a normal stop-and-copy GC strategy. That's really all
> > there is to it.
>
> Tell us the details! A single generation, or multiple generations? Do
> objects
> get tenured eventua
felix winkelmann scripsit:
> The secondary
> heap follows a normal stop-and-copy GC strategy. That's really all
> there is to it.
Tell us the details! A single generation, or multiple generations? Do objects
get tenured eventually?
--
But you, Wormtongue, you have done what you could for your
On 12/20/05, Sergey Khorev <[EMAIL PROTECTED]> wrote:
> fw> > One has to distinguish between the initial garbage collector, which
> moves
> fw> > nongarbage from the (garbage) stack to the heap, and garbage collections
> fw> > within the heap. The first is part of the Chicken way of doing
> busi
fw> > One has to distinguish between the initial garbage collector, which moves
fw> > nongarbage from the (garbage) stack to the heap, and garbage collections
fw> > within the heap. The first is part of the Chicken way of doing business;
fw> > the second could probably be replaced by a different G
On 12/20/05, John Cowan <[EMAIL PROTECTED]> wrote:
> Sergey Khorev scripsit:
>
> > The idea was to use Chicken as an embedded interpreter but don't have
> > two GC's in one process.
>
> One has to distinguish between the initial garbage collector, which moves
> nongarbage from the (garbage) stack t
Sergey Khorev scripsit:
> The idea was to use Chicken as an embedded interpreter but don't have
> two GC's in one process.
One has to distinguish between the initial garbage collector, which moves
nongarbage from the (garbage) stack to the heap, and garbage collections
within the heap. The first
fw> > Generally speaking, a replacement of the runtime system should be
fw> > possible, but maybe not desirable. I think that the special stack
fw> > allocation technique employed by CHICKEN will probably integrate badly
fw> > with most other language runtimes and that forcing the CHICKEN runtime o
On 12/16/05, Thomas Chust <[EMAIL PROTECTED]> wrote:
>
> Generally speaking, a replacement of the runtime system should be
> possible, but maybe not desirable. I think that the special stack
> allocation technique employed by CHICKEN will probably integrate badly
> with most other language runtimes
fw> > 2. I saw there were some issues on Win32, especially with MinGW. I wonder
fw> > whether they have been resolved or not, so I can put my hands on them.
fw> Yes, please. Brandon is currently wrestling with CMake, but perhaps
fw> you can try the current snapshot yourself and report any build pro
On Fri, 16 Dec 2005, SergeyKhorev wrote:
> [...] So I was wondering how difficult would be a task replacing Chicken
> runtime system? My idea is to keep current runtime interface but
> substitute the body with calls to the host language other than just C.
> Has anyone looked into this or even t
On 12/16/05, Sergey Khorev <[EMAIL PROTECTED]> wrote:
> 1. I see there is an item in the TASKS file named "an alternative frontend".
> Does this mean "compile programs from other languages to the C code which uses
> Chicken runtime"?
Yes, at various stages I thought about translating other langua
Finally I've got some spare time to spent to Chicken.
1. I see there is an item in the TASKS file named "an alternative frontend".
Does this mean "compile programs from other languages to the C code which uses
Chicken runtime"?
2. I saw there were some issues on Win32, especially with MinGW. I won
14 matches
Mail list logo
