Prefer relative links for Nim documentation
This is more friendly to those browsing the documentation without a network connection. The nim-doc package in Debian allows this, for example. Also, the domain name being used was not consistent. It could have been either nim-lang.org or nim-lang.github.io, and those reading the stable docs could have found themselves suddenly reading the devel docs instead.
This commit is contained in:
parent
93461aee34
commit
72147c9ba4
5 changed files with 10 additions and 10 deletions
|
|
@ -237,7 +237,7 @@ Call with raw string literal
|
||||||
----------------------------
|
----------------------------
|
||||||
|
|
||||||
This is used, for example, in the ``bindSym`` examples
|
This is used, for example, in the ``bindSym`` examples
|
||||||
[here](http://nim-lang.org/docs/manual.html#macros-bindsym) and with
|
[here](manual.html#macros-bindsym) and with
|
||||||
``re"some regexp"`` in the regular expression module.
|
``re"some regexp"`` in the regular expression module.
|
||||||
|
|
||||||
Concrete syntax:
|
Concrete syntax:
|
||||||
|
|
@ -902,7 +902,7 @@ as the compiler needs to know the type somehow (which it can infer from
|
||||||
the given assignment).
|
the given assignment).
|
||||||
|
|
||||||
This is not the same AST for all uses of ``var``. See
|
This is not the same AST for all uses of ``var``. See
|
||||||
[Procedure declaration](http://nim-lang.org/docs/macros.html#statements-procedure-declaration)
|
[Procedure declaration](macros.html#statements-procedure-declaration)
|
||||||
for details.
|
for details.
|
||||||
|
|
||||||
Let section
|
Let section
|
||||||
|
|
@ -1361,7 +1361,7 @@ Template declaration
|
||||||
|
|
||||||
Templates (as well as macros, as we'll see) have a slightly expanded AST when
|
Templates (as well as macros, as we'll see) have a slightly expanded AST when
|
||||||
compared to procs and iterators. The reason for this is [term-rewriting
|
compared to procs and iterators. The reason for this is [term-rewriting
|
||||||
macros](http://nim-lang.org/docs/manual.html#term-rewriting-macros). Notice
|
macros](manual.html#term-rewriting-macros). Notice
|
||||||
the ``nnkEmpty()`` as the second argument to ``nnkProcDef`` and
|
the ``nnkEmpty()`` as the second argument to ``nnkProcDef`` and
|
||||||
``nnkIteratorDef`` above? That's where the term-rewriting macros go.
|
``nnkIteratorDef`` above? That's where the term-rewriting macros go.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -188,7 +188,7 @@ the old name and introduce a new name:
|
||||||
type Barz = enum baz0, baz1 {.deprecated.}, baz2
|
type Barz = enum baz0, baz1 {.deprecated.}, baz2
|
||||||
|
|
||||||
|
|
||||||
See also `Deprecated <https://nim-lang.org/docs/manual.html#pragmas-deprecated-pragma>`_
|
See also `Deprecated <manual.html#pragmas-deprecated-pragma>`_
|
||||||
pragma in the manual.
|
pragma in the manual.
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -213,7 +213,7 @@ as well as ``testament`` and guarantee they stay in sync.
|
||||||
assert "baz".addBar == "bazBar"
|
assert "baz".addBar == "bazBar"
|
||||||
result = a & "Bar"
|
result = a & "Bar"
|
||||||
|
|
||||||
See `parentDir <https://nim-lang.github.io/Nim/os.html#parentDir%2Cstring>`_
|
See `parentDir <os.html#parentDir,string>`_
|
||||||
example.
|
example.
|
||||||
|
|
||||||
The RestructuredText Nim uses has a special syntax for including code snippets
|
The RestructuredText Nim uses has a special syntax for including code snippets
|
||||||
|
|
|
||||||
|
|
@ -164,7 +164,7 @@ you can pass ``--gc:`` on the compile command with the choosed garbage collector
|
||||||
|
|
||||||
The same Nim code can be compiled to use any of the garbage collectors;
|
The same Nim code can be compiled to use any of the garbage collectors;
|
||||||
the Nim syntax generally will not change from one garbage collector to another.
|
the Nim syntax generally will not change from one garbage collector to another.
|
||||||
No garbage collector is used for `JavaScript and NodeJS <https://nim-lang.github.io/Nim/backends.html#backends-the-javascript-target>`_ compilation targets.
|
No garbage collector is used for `JavaScript and NodeJS <backends.html#backends-the-javascript-target>`_ compilation targets.
|
||||||
`NimScript <https://nim-lang.github.io/Nim/nims.html>`_ target uses Nim VM garbage collector.
|
`NimScript <nims.html>`_ target uses Nim VM garbage collector.
|
||||||
|
|
||||||
If you are new to Nim and just starting, the default garbage collector is balanced to fit most common use cases.
|
If you are new to Nim and just starting, the default garbage collector is balanced to fit most common use cases.
|
||||||
|
|
|
||||||
|
|
@ -20,7 +20,7 @@ The standard distribution ships with the following tools:
|
||||||
- | `C2nim <https://github.com/nim-lang/c2nim/blob/master/doc/c2nim.rst>`_
|
- | `C2nim <https://github.com/nim-lang/c2nim/blob/master/doc/c2nim.rst>`_
|
||||||
| C to Nim source converter. Translates C header files to Nim.
|
| C to Nim source converter. Translates C header files to Nim.
|
||||||
|
|
||||||
- | `niminst <https://nim-lang.org/docs/niminst.html>`_
|
- | `niminst <niminst.html>`_
|
||||||
| niminst is a tool to generate an installer for a Nim program.
|
| niminst is a tool to generate an installer for a Nim program.
|
||||||
|
|
||||||
- | `nimgrep <nimgrep.html>`_
|
- | `nimgrep <nimgrep.html>`_
|
||||||
|
|
|
||||||
|
|
@ -13,8 +13,8 @@ include "system/inclrtl"
|
||||||
## tree (`AST`:idx:). Macros operate on this tree.
|
## tree (`AST`:idx:). Macros operate on this tree.
|
||||||
##
|
##
|
||||||
## See also:
|
## See also:
|
||||||
## * `macros tutorial <https://nim-lang.github.io/Nim/tut3.html>`_
|
## * `macros tutorial <tut3.html>`_
|
||||||
## * `macros section in Nim manual <https://nim-lang.github.io/Nim/manual.html#macros>`_
|
## * `macros section in Nim manual <manual.html#macros>`_
|
||||||
|
|
||||||
## .. include:: ../../doc/astspec.txt
|
## .. include:: ../../doc/astspec.txt
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue