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

Fix comment typos

Browse source
This commit is contained in:
Olly Betts 2014-05-18 20:20:30 +12:00
commit def3c08943
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
Examples/test-suite/lua/operator_overload_runme.lua
View file

@ -1,4 +1,4 @@
-- demo of lua swig capacilities (operator overloading) -- demo of lua swig capacities (operator overloading)
require("import") -- the import fn require("import") -- the import fn
import("operator_overload") -- import lib import("operator_overload") -- import lib
@ -33,7 +33,7 @@ assert(b>=c)
assert(b>d) assert(b>d)
assert(b>=d) assert(b>=d)
-- lua does not support += operators: skiping -- lua does not support += operators: skipping
-- test + -- test +
f=Op(1) f=Op(1)
@ -50,7 +50,7 @@ assert(f/g==Op(1))
--lua 5.0.2 defines that unary - is __unm(self,nil) --lua 5.0.2 defines that unary - is __unm(self,nil)
--lua 5.1.2 defines that unary - is __unm(self,self) --lua 5.1.2 defines that unary - is __unm(self,self)
--C++ expectes unary - as operator-() --C++ expects unary - as operator-()
--however the latest version of SWIG strictly checks the number of args --however the latest version of SWIG strictly checks the number of args
--and will complain if too many args are provided --and will complain if too many args are provided
--therefore disabling these tests for now --therefore disabling these tests for now
@ -79,7 +79,7 @@ assert(tostring(Op(1))=="Op(1)")
assert(tostring(Op(-3))=="Op(-3)") assert(tostring(Op(-3))=="Op(-3)")
-- check that operator overloads are correctly propogated down inheritance hierarchy -- check that operator overloads are correctly propagated down inheritance hierarchy
a_d=OpDerived() a_d=OpDerived()
b_d=OpDerived(5) b_d=OpDerived(5)