http://d.puremagic.com/issues/show_bug.cgi?id=280

           Summary: Doc of GC
           Product: D
           Version: 0.163
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Phobos
        AssignedTo: bugzilla@digitalmars.com
        ReportedBy: benoit@tionex.de


After telling this every week at minimum one person... Please say it in the doc:

The GC enable/disable are not implemented.


-- 

d-bugmail@puremagic.com wrote:
> http://d.puremagic.com/issues/show_bug.cgi?id=280
> 
>            Summary: Doc of GC
>            Product: D
>            Version: 0.163
>           Platform: PC
>         OS/Version: All
>             Status: NEW
>           Severity: normal
>           Priority: P2
>          Component: Phobos
>         AssignedTo: bugzilla@digitalmars.com
>         ReportedBy: benoit@tionex.de
> 
> 
> After telling this every week at minimum one person... Please say it in the
> doc:
> 
> The GC enable/disable are not implemented.

I think it would be trivial to enable this feature.  Try adding these lines to the top of internal/gc/gcx.d - fullcollectshell():

    if (gcx.disabled > 0)
        return 0;

This should force the GC to allocate a new pool if all existing pools are full instead of first attempting a collect.

Sean Kelly wrote:
> 
> I think it would be trivial to enable this feature.  Try adding these lines to the top of internal/gc/gcx.d - fullcollectshell():
> 
>     if (gcx.disabled > 0)
>         return 0;

Correction, the above should be:

     if (disabled > 0)
         return 0;

I forgot this code is in the Gcx struct.


Sean

http://d.puremagic.com/issues/show_bug.cgi?id=280


smjg@iname.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |smjg@iname.com
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Comment #3 from smjg@iname.com  2006-11-02 17:38 -------
Issue 170 is logged as fixed in DMD 0.165.


--