From b89495ef0f6bb60a3296fbaa7c4397dcd269f73d Mon Sep 17 00:00:00 2001 From: Araq Date: Mon, 30 Jun 2014 19:39:57 +0200 Subject: corrected backends.txt --- doc/backends.txt | 18 +++++++----------- 1 file changed, 7 insertions(+), 11 deletions(-) (limited to 'doc/backends.txt') diff --git a/doc/backends.txt b/doc/backends.txt index 0ab682c29..26576e733 100644 --- a/doc/backends.txt +++ b/doc/backends.txt @@ -6,12 +6,7 @@ :Version: |nimrodversion| .. contents:: - - "If we all reacted the same way, we'd be predictable, and there's - always more than one way to view a situation. What's true for the - group is also true for the individual. It's simple: overspecialize, - and you breed in weakness. It's slow death." -- Major Motoko - Kusanagi + "Heresy grows from idleness." -- Unknown. Introduction @@ -160,7 +155,7 @@ Create a ``calculator.nim`` file with the following content: .. code-block:: nimrod {.compile: "logic.c".} - proc addTwoIntegers(a, b: int): int {.importc.} + proc addTwoIntegers(a, b: cint): cint {.importc.} when isMainModule: echo addTwoIntegers(3, 7) @@ -407,7 +402,8 @@ can then attach a GC to this thread via initGC() At the moment this support is still experimental so you need to expose these -functions yourself or submit patches to request a public API. If the Nimrod -code you are calling is short lived, another possible solution is to disable -the garbage collector and enable it after the call from your background -thread. +functions yourself or submit patches to request a public API. + +It is **not** safe to disable the garbage collector and enable it after the +call from your background thread even if the code you are calling is short +lived. -- cgit 1.4.1-2-gfad0