On 11/08/2010 06:12 PM, Alexander Haeckel wrote:
> there seems to be a problem in srecode-getset.el. Within
> the method (srecode-insert-getset) the assignment
> (setq field (srecode-query-for-field class)) sets field to
> (#<TAG name>) instead of #<TAG name>.
> Subsequently (semantic-tag-p field) evaluates unexpectedly
> to nil, which falsely causes a error.
> I don't know if the naive fix
> (setq field (car (srecode-query-for-field class)))
> is a sufficient solution or if there is a deeper problem
> within srecode-query-for-field.
The best strategy would be to update srecode-query-for-field to
always return the right thing. It is only used in that one spot at the
moment, so it could be updated to be sure to return one tag or a string
If someone wants to make a patch I can apply, that would be great.