Nimrod -> Nim

This commit is contained in:
Dennis Felsing 2015-02-03 08:59:41 +01:00
parent af1e9ae846
commit a978a2f0eb
1 changed files with 9 additions and 9 deletions

View File

@ -1,4 +1,4 @@
If you are looking for the official FAQ then you can find it [here](http://nimrod-lang.org/question.html) If you are looking for the official FAQ then you can find it [here](http://nim-lang.org/question.html)
# How can I help? # How can I help?
@ -11,15 +11,15 @@ For beginners I suggest to implement missing parts of the standard library or so
* libraries that deal with multi-media * libraries that deal with multi-media
* etc. * etc.
# How does the Nimrod compiler's versioning scheme work? # How does the Nim compiler's versioning scheme work?
Versions with a trailing odd number are considered to be "in-development", these are unstable "bleeding-edge" versions of the compiler which you can get from Github. Versions with an even number are releases. E.g. 0.9.0 is a release version, 0.9.1 is an in-development version. Versions with a trailing odd number are considered to be "in-development", these are unstable "bleeding-edge" versions of the compiler which you can get from Github. Versions with an even number are releases. E.g. 0.9.0 is a release version, 0.9.1 is an in-development version.
# Will Nimrod have block comments? # Will Nim have block comments?
Most probably not. Reasons for avoiding them are: Most probably not. Reasons for avoiding them are:
* If proper block comments exist, they should be nestable. This means you cannot tokenize Nimrod with regular expressions anymore. * If proper block comments exist, they should be nestable. This means you cannot tokenize Nim with regular expressions anymore.
* The editor can be used to put "#" in front of every line. * The editor can be used to put "#" in front of every line.
* "when false" is not a bad solution. At least syntax is still checked for deactivated code. * "when false" is not a bad solution. At least syntax is still checked for deactivated code.
* discard """ """" is another solution. * discard """ """" is another solution.
@ -33,20 +33,20 @@ Most probably not. Reasons for avoiding them are:
# Where can I find code examples? # Where can I find code examples?
You can find examples in the [examples/](https://github.com/Araq/Nimrod/tree/master/examples) directory. There are also many other examples available on [Rosetta Code](http://rosettacode.org/wiki/Nimrod). You can find examples in the [examples/](https://github.com/Araq/Nim/tree/master/examples) directory. There are also many other examples available on [Rosetta Code](http://rosettacode.org/wiki/Nim).
# Why are unsigned types discouraged? # Why are unsigned types discouraged?
* http://critical.eschertech.com/2010/04/07/danger-unsigned-types-used-here/ * http://critical.eschertech.com/2010/04/07/danger-unsigned-types-used-here/
* http://forum.nimrod-lang.org/t/313#1631 * http://forum.nim-lang.org/t/313#1631
# Why are tabs forbidden? # Why are tabs forbidden?
Tabs are treated differently by different tools and editors. Because indentation is so important in Nimrod it is much simpler to outright forbid tabs in source code than to risk the mixing of tabs and spaces. Guido van Rossum of Python himself has said that if he were to design Python again he would forbid tabs. Tabs are treated differently by different tools and editors. Because indentation is so important in Nim it is much simpler to outright forbid tabs in source code than to risk the mixing of tabs and spaces. Guido van Rossum of Python himself has said that if he were to design Python again he would forbid tabs.
Nimrod is certainly not unique in forbidding tabs. [YAML](http://www.yaml.org/faq.html) does the same. Nim is certainly not unique in forbidding tabs. [YAML](http://www.yaml.org/faq.html) does the same.
# I get an error trying to compile Nimrod on Windows. # I get an error trying to compile Nim on Windows.
If this error looks something like the following: If this error looks something like the following: