removed unsigned part, as it is not a specific issue for python programmers
This commit is contained in:
parent
b4ea9f47db
commit
848c58e320
|
@ -97,12 +97,6 @@ Nim arrays can also be indexed from any number. That is, ``z: array[1..4, int]``
|
|||
|
||||
In Nim you are strongly discouraged from using pointers in Nim, and you can accomplish almost everything you'd otherwise use pointers for with normal arguments, "var" arguments, variables, and "ref".
|
||||
|
||||
### Unsigned integers
|
||||
|
||||
Nim strongly discourages the use of unsigned integers, as it's considered unnecessary and somewhat unsafe* for most applications. The unsigned types uint, uint8/16/32/64 are available by default, but the arithmetic and binary functions are not defined. If you do need to do arithmetic on unsigned integers, you need to import the **unsigned** module.
|
||||
|
||||
*See: http://critical.eschertech.com/2010/04/07/danger-unsigned-types-used-here/
|
||||
|
||||
|
||||
### Object-Orientation
|
||||
|
||||
|
|
Loading…
Reference in New Issue