Remove question about block comments because they have been added
This commit is contained in:
parent
2f4b6ff677
commit
7b59462366
|
@ -14,15 +14,6 @@ For beginners I suggest to implement missing parts of the standard library or so
|
||||||
|
|
||||||
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 Nim have block comments?
|
|
||||||
|
|
||||||
Most probably not. Reasons for avoiding them are:
|
|
||||||
|
|
||||||
* 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.
|
|
||||||
* "when false" is not a bad solution. At least syntax is still checked for deactivated code.
|
|
||||||
* discard """ """" is another solution.
|
|
||||||
|
|
||||||
# Why is it case/underscore insensitive?
|
# Why is it case/underscore insensitive?
|
||||||
|
|
||||||
* Identifiers which only differ in case are bad style. If the programming language treats them the same the programmer needs to come up with different names for different things.
|
* Identifiers which only differ in case are bad style. If the programming language treats them the same the programmer needs to come up with different names for different things.
|
||||||
|
|
Loading…
Reference in New Issue