Re: [pygccxml-development] Additional attribute functionality

[Ben S. <bsc...@lu...>]

Hi Roman,
   Another thing to keep in mind for after 1.0 is that the scopedef is
very difficult to work with.
When I write class_.member_function("foobar"), I expect either a value
or None to be returned. I don't expect an exception to be thrown
likewise, I'd like to see class_.member_functions("foobar") to return a
list of declarations, zero if no declaration matches. Again, no
exception should be through.
Then I can take the list and manipulate it like a normal python list.
=20
Cheers
Ben
=20


________________________________

	From: Roman Yakovenko [mailto:rom...@gm...]=20
	Sent: Tuesday, December 04, 2007 12:23 AM
	To: Ben Schleimer
	Cc: pyg...@li...
	Subject: Re: [pygccxml-development] Additional attribute
functionality
=09
=09
	On Dec 4, 2007 10:11 AM, Ben Schleimer
<bsc...@lu...> wrote:
=09

		Hi Roman,
		   I have another patch here which contains the previous
patch and adds size,align,offset info the correct classes.
		Again, I hope it makes sense. One thing I would change
is more the __read_size/align into the method reading the types and
classes.


	I will apply it later.
	=20

	=09
		Maybe it makes sense to have class_t inherit from type_t
because they are very similar?
	=09
	=09


	You just discovered the awful mistake I made. You are absolutely
right - everything should derive from type_t. I cannot fix the mistake,
without introducing backward compatibility problems for the users.  I
prefer to implement this change after official 1.0 release of the
project, where I will allow to myself to break it.
=09
	--=20
	Roman Yakovenko
	C++ Python language binding
	http://www.language-binding.net/=20