jyapayne/Nim
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

doc/tut2.txt: clarified usage of static/dynamic binding

Browse source 
The original text was slightly misleading in that it could be read that newLit and newPlus could not be implemented as methods; 
this is untrue, because newPlus could also be impleented as a method. The reason that newLit can't be implemented as a
method is that its first argument (x: int) has a non-object type.
This commit is contained in:
Daniel Kullmann 2015-01-11 00:15:49 +01:00
commit 451b943a01
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/tut2.txt
View file

@ -304,8 +304,8 @@ Procedures always use static dispatch. For dynamic dispatch replace the
echo eval(newPlus(newPlus(newLit(1), newLit(2)), newLit(4)))
Note that in the example the constructors ``newLit`` and ``newPlus`` are procs
because they should use static binding, but ``eval`` is a method because it
requires dynamic binding.
because it makes more sense for them to use static binding, but ``eval`` is a
method because it requires dynamic binding.
In a multi-method all parameters that have an object type are used for the
dispatching: