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

fixed document typos

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@8159 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
Jason Stewart 2006-01-01 06:35:51 +00:00
commit eefe20390c
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
SWIG/Lib/typemaps/fragments.swg
View file

@ -174,7 +174,7 @@
Fragments can be "type specialized". The syntax is as follows
%fragment("name","header") { a type independent fragment }
%fragment("name" {Type}, "header") {typethe dependent fragment }
%fragment("name" {Type}, "header") { a type dependent fragment }
and they can also, as typemaps, be used inside templates, for exampe:
@ -194,7 +194,7 @@
fundamental for automatic typemap and template specialization.
Fragments and automatic typemap specialozation:
Fragments and automatic typemap specialization:
===============================================
Since fragments can be type specialized, they can be elegantly used
@ -203,13 +203,13 @@
For example, if you have something like:
%fragment("incode"{float}, "header") {
float in_mehtod_float(PyObject *obj) {
float in_method_float(PyObject *obj) {
...
}
}
%fragment("incode"{long}, "header") {
float in_mehtod_long(PyObject *obj) {
float in_method_long(PyObject *obj) {
...
}
}
@ -226,7 +226,7 @@
then the proper "incode"{float,double} fragment will be included,
and the proper in_method_{float,double} will be called.
Since this is a recurrent fragmen use, we provide a couple of
Since this is a recurrent fragment use, we provide a couple of
macros that make the automatic generation of typemaps easier: