Re: [C++-sig] pygccxml KeyError

2011-12-19 Thread Roman Yakovenko
On Sat, Dec 17, 2011 at 2:23 AM, Davidson, Josh wrote: > Hopefully, there’s enough information in the traceback, but if not I can try > to sanitize an example.  I’m on rev 1856. More or less. Sorry for late response, I was pretty busy. >   File "c:\Python26\lib\site-packages\pygccxml\parser\proj

Re: [C++-sig] EXTERNAL: Re: pygccxml KeyError

2011-12-19 Thread Davidson, Josh
Short of modifying the distribution, I don't see any way within Py++ to change the type of reader. It seems to be hardcoded to project_reader_t: def __parse_declarations( self, files, gccxml_config, compilation_mode, cache, indexing_suite_version ): if None is gccxml_config:

Re: [C++-sig] EXTERNAL: Re: pygccxml KeyError

2011-12-19 Thread Davidson, Josh
May have been a bit too quick to respond. Looks like setting the compilation mode can be used to have the project_reader_t use a source_reader_t. Sorry about that. -Original Message- From: Davidson, Josh Sent: Monday, December 19, 2011 1:00 PM To: 'Development of Python/C++ integratio

Re: [C++-sig] EXTERNAL: Re: pygccxml KeyError

2011-12-19 Thread Davidson, Josh
Actually, it is using a source_reader_t by default. __parse_declarations invokes __parse_file_by_file, which uses a source_reader_t (line 236) to parse each file. It then bombs out after parsing all of the files when it calls _join_class_hierarchy. I continue to have this issue with various c

Re: [C++-sig] EXTERNAL: Re: pygccxml KeyError

2011-12-19 Thread Roman Yakovenko
On Mon, Dec 19, 2011 at 10:24 PM, Davidson, Josh wrote: > Actually, it is using a source_reader_t by default.  __parse_declarations > invokes __parse_file_by_file, which uses a source_reader_t (line 236) to > parse each file.  It then bombs out after parsing all of the files when it > calls _jo

Re: [C++-sig] EXTERNAL: Re: pygccxml KeyError

2011-12-19 Thread Davidson, Josh
Including everything into a single header does work, so it looks like there is a problem with the joining process. Well, it builds anyways. I still get compilation error W1050 telling me that I didn't specify a call policies (I did and they show up in the generated code). These are the Py++ s

[C++-sig] Complaint about missing call policies, when they are in fact specified

2011-12-19 Thread Davidson, Josh
I'm adding return value call policies to methods of a class as follows: mb.class_("SerialStore").member_functions(lambda decl: decl.name.startswith("getSim")).call_policies = \ call_policies.return_internal_reference() --

Re: [C++-sig] Complaint about missing call policies, when they are in fact specified

2011-12-19 Thread Roman Yakovenko
On Mon, Dec 19, 2011 at 9:01 PM, Davidson, Josh wrote: > I'm adding return value call policies to methods of a class as follows: >        mb.class_("SerialStore").member_functions(lambda decl: > decl.name.startswith("getSim")).call_policies = \ >            call_policies.return_internal_reference