Achilleas Margaritis wrote:
Steven Burns wrote:
No, __fastcall is not portable, but it's largely irrelevant to the algorithm. I think the top-1 question will be: how does it handle cycles?
Steven
Cycles are handled as in every other garbage collector, i.e. objects connected cyclically do not remain for ever in memory.
"Larry Evans" <cppljevans@cox-internet.com> wrote in message news:fclt2h$2v4$1@sea.gmane.org...
On 09/16/07 16:56, Achilleas Margaritis wrote:
Dear boost developers,
You can find a new version of my portable precise C++ garbage collector in vault/memory.
The file:
src/cppgc.cpp
contains:
void __fastcall _gc_traits::scan(register void *ptr) {
is __fastcall portable?
I uploaded a new version in the vault which does not have __fastcall. But it's noticeably slower without it, so I might introduce a macro in the future for those platforms that support it.