inlining of the write barrier for dlls

1 files changed, 17 insertions, 17 deletions

diff --git a/doc/nimrodc.txt b/doc/nimrodc.txt
index 997146ede..733c83f0c 100755
--- a/doc/nimrodc.txt
+++ b/doc/nimrodc.txt
@@ -69,23 +69,23 @@ generated files.
 However, the generated C code is not platform independent. C code generated for

 Linux does not compile on Windows, for instance. The comment on top of the

 C file lists the OS, CPU and CC the file has been compiled for.

-
-
-DLL generation
-==============
-
-Nimrod supports the generation of DLLs. However, there must be only one 
-instance of the GC per process/address space. This instance is contained in
-``nimrtl.dll``. This means that every generated Nimrod DLL depends
-on ``nimrtl.dll``. To generate the "nimrtl.dll" file, use the command::
-  
-  nimrod c -d:release lib/nimrtl.nim
-
-To link to ``nimrtl.dll`` use the command::
-
-  nimrod c -d:useNimRtl myprog.nim
-
-
+

+

+DLL generation

+==============

+

+Nimrod supports the generation of DLLs. However, there must be only one 

+instance of the GC per process/address space. This instance is contained in

+``nimrtl.dll``. This means that every generated Nimrod DLL depends

+on ``nimrtl.dll``. To generate the "nimrtl.dll" file, use the command::

+  

+  nimrod c -d:release lib/nimrtl.nim

+

+To link against ``nimrtl.dll`` use the command::

+

+  nimrod c -d:useNimRtl myprog.nim

+

+

 

 Additional Features

 ===================