Open GoogleCodeExporter opened 8 years ago
Javier, do we still want to do this? It seems like the PSEngine interface
obviates this.
Original comment by miata...@gmail.com
on 24 Nov 2009 at 6:15
I think both reasons still aply :
- even though PSEngine deals with naked pointers, many times it has to unwrap
ids to put into collections,
which introduces delays
- many classes have method pairs where one method returns a pointer (for
PSEngine) and the other an Id. It
would be good to eliminate that redundancy. Figuring out how to pass Ids
cleanly through SWIG, or compiling
Ids as pointers are the 2 ways I can think of for achieving that.
at this point I care more about the method redundancy for SWIG wrapping, than
any performance gains this
may introduce, so if there is a better way to simplify SWIG wrapping, let's
talk about it.
Original comment by javier.barreiro@gmail.com
on 24 Nov 2009 at 6:53
Original issue reported on code.google.com by
miata...@gmail.com
on 15 Sep 2009 at 4:00