L164 實現不是完全模組化和過度使用巨集。也許有朝一日所有的C編譯器現在不能作的蠻力擴充套件嵌入模組碼能做到，但是現在他們似乎是不足的。

 The implementation is not very modular and seriously overuses macros. Perhaps someday all C compilers will do as good a job inlining modular code as can now be done by brute-force expansion, but now, enough of them seem not to.

一些編譯器傳送許多的警告，關於程式碼死掉/不能找到僅僅在一些平臺上，並且也關於一些故意不用的無符號型別。所有一隻能被忽略的原因。

Some compilers issue a lot of warnings about code that is dead/unreachable only on some platforms, and also about intentional uses of negation on unsigned types. All known cases of each can be ignored.

L178 MSSPACES

如果定義了MSSPACES，然後加入malloc,free,等.中，這個檔案也定義 mspace_malloc, mspace_free,等。這些是常規版本malloc採取"mspace"引數獲得引用create_mspace，去控制所有的內部記錄。如果 ONLY_MSPACES被定義，僅這些版本被編譯。這樣如果你想使用這個記憶體分配器為僅僅一些記憶體分配並且你的系統malloc作其他的，你可以僅編譯ONLY_MSPACES並然後做一些事情像...

   static mspace myspace = create_mspace(0,0);//例子

   #define mymalloc(bytes)  mspace_malloc(mymspace, bytes)

* MSPACES
  If MSPACES is defined, then in addition to malloc, free, etc., this file also defines mspace_malloc, mspace_free, etc. These are versions of malloc routines that take an "mspace" argument obtained using create_mspace, to control all internal bookkeeping. If ONLY_MSPACES is defined, only these versions are compiled. So if you would like to use this allocator for only some allocations, and your system malloc for others, you can compile with ONLY_MSPACES and then do something like...
    static mspace mymspace = create_mspace(0,0); // for example
    #define mymalloc(bytes)  mspace_malloc(mymspace, bytes)

L189 註解：如果你僅需一個mspace例項，你可以替換用USE_DL_PREFIX去重注全域性malloc

你同樣能建立執行緒區域性記憶體分配儲存mspaces像區域性執行緒。例如：

     static __thread mspace tlms = 0;

     void* tlmalloc(size_t bytes)

     {

          if(tlms == 0) tlms = create_mspace(0,0);

          return mspace_malloc(tlms, bytes); 

     }

     void tlfree(void* mem) { mspace_free(tlms,mem);}

除非 FOOTERS是定義的，每一個mspace是獨立完成的，你不能從一個自由分配到另一個（儘管一致性檢查是弱的，錯誤的用法不總是被捕獲）。如果FOOTERS被定義，每一個塊攜帶著一個標籤標明它源於mspace，並且釋放指向它的源spaces。

  (Note: If you only need one instance of an mspace, you can instead use "USE_DL_PREFIX" to relabel the global malloc.)

  You can similarly create thread-local allocators by storing mspaces as thread-locals. For example:
    static __thread mspace tlms = 0;
    void*  tlmalloc(size_t bytes) {
      if (tlms == 0) tlms = create_mspace(0, 0);
      return mspace_malloc(tlms, bytes);
    }
    void  tlfree(void* mem) { mspace_free(tlms, mem); }

  Unless FOOTERS is defined, each mspace is completely independent. You cannot allocate from one and free to another (although conformance is only weakly checked, so usage errors are not always caught). If FOOTERS is defined, then each chunk carries around a tag indicating its originating mspace, and frees are directed to their originating spaces.

L208--------------------------------編譯選項-----------------------------------------------------

謹慎建立size_t型別數學常量值的定義。一些系統，預設的值不是自動適應size_t精度除非他們明確的定義，你也能使用符號值MAX_SIZE_T，SIZE_T_ONE,等如下。

WIN32                       預設：定義如果 _WIN32定義

定義WIN32建立預設為MS環境並編譯器。另外預設為unix。注意的是，似乎有一些malloc的情況下，這可能不是一個純粹的簡易替換為WIN32的malloc：隨機檢視失敗從Win32 GDI API的原由也許是在一些視訊驅動執行當畫素快取被分配，並且虛擬快取溢位的BUG。因為 dlmalloc使用一個小的預設粒度為64k的，畫素快取可能經常跨虛擬快取範圍分配當用微軟的記憶體分配器時。你能解決這個使用VirtualAlloc（）和VirtualFree（）為所有的畫素快取寧可用malloc()。如果這是不可能的，重新編譯這個malloc帶著一個大的DEFAULT_GRANULARITY。

 -------------------------  Compile-time options ---------------------------

Be careful in setting #define values for numerical constants of typesize_t. On some systems, literal values are not automatically extended to size_t precision unless they are explicitly casted. You can also use the symbolic values MAX_SIZE_T, SIZE_T_ONE, etc below.

WIN32                    default: defined if _WIN32 defined
  Defining WIN32 sets up defaults for MS environment and compilers.  Otherwise defaults are for unix. Beware that there seem to be some cases where this malloc might not be a pure drop-in replacement for Win32 malloc:Random-looking failures from Win32 GDI API's (eg; SetDIBits()) may be due to bugs in some video driver implementations when pixel buffers are malloc()ed, and the region spans more than one VirtualAlloc()ed region. Because dlmalloc uses a small (64Kb)
  default granularity, pixel buffers may straddle virtual allocation regions more often than when using the Microsoft allocator.  You can avoid this by using VirtualAlloc() and VirtualFree() for all pixel buffers rather than using malloc().  If this is not possible, recompile this malloc with a larger DEFAULT_GRANULARITY.