Thread: [pygccxml-development] Gripe: read-only parser config properties
Brought to you by:
mbaas,
roman_yakovenko
From: Gustavo C. <gjc...@gm...> - 2007-12-20 15:08:06
|
Most properties in: http://www.language-binding.net/pygccxml/apidocs/pygccxml.parser.config.config_t-class.html#include_paths are read-only. And in addition there is not even a setter method. This leads me to support a bad coding pattern: everything must be set in the constructor, and is frozen afterwards. Thoughts? -- Gustavo J. A. M. Carneiro INESC Porto, Telecommunications and Multimedia Unit "The universe is always one step beyond logic." -- Frank Herbert |
From: Roman Y. <rom...@gm...> - 2007-12-20 15:29:39
|
On Dec 20, 2007 5:08 PM, Gustavo Carneiro <gjc...@gm...> wrote: > Most properties in: > > http://www.language-binding.net/pygccxml/apidocs/pygccxml.parser.config.config_t-class.html#include_paths > > are read-only. And in addition there is not even a setter method. This > leads me to support a bad coding pattern: everything must be set in the > constructor, and is frozen afterwards. > > Thoughts? Why do you want to change it after construction? What is your use case? P.S. I don't mind to add setters to the class -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/ |