|
From: Allen B. <al...@vr...> - 2006-10-10 14:50:57
|
Roman Yakovenko wrote: >On 10/10/06, Allen Bierbaum <al...@vr...> wrote: > > >>Okay, so my problem is that I am wrapping a class you can see here: >> >> > >I just commited the answer to your question. Take a look on >how_to.rest document, >last question: How to deal with template on return type functions? > > > I just read this document and although it describes what is causing Py++ to generate the code I am not sure it answers the issues I am having: 1. Only the last method wrapped is able to be called from python, so why wrap the others? 2. I think I see what you are getting at in the solution section about renaming the methods automatically, but this only exposes the ones that are called in the header files that gccxml is compiling. In my case (and I think probably in most cases where this will come up), I want to create "get_value" methods for many more types then gccxml actually saw. Is there any way to know of to force these methods to be instantiated similar to what we do with class templates? 3. Why do I have to change the function name to demangled name, can't I just change the alias to what I want the method to appear as and rely upon Py++ to use casts to get the correct method? (at least with gcc 4 I get compiler errors trying to do the equivalent of your correct code and get "&::environment_t::get_value<std::string>". -Allen >>PS. I just tried the latest svn version of Py++ on my largest project >>and things seem to be working fine. >> >> > >Can you provide feedback on add_properties algorithms? The >documentation in properties.rest > document? > >Also can you read and correct the documentation the project has? > >Thank you. > > > |
