cadey
/
nim-wiki
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

removed unsigned part, as it is not a specific issue for python programmers

This commit is contained in:
ReneSac 2015-04-03 20:43:17 -03:00
parent b4ea9f47db
commit 848c58e320
1 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Nim-for-Python-Programmers.md
View File

@ -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". 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 ### Object-Orientation