(In reply to Trevor Saunders (:tbsaunde) from comment #22)
> or we could do what we do for a bunch of other atk methods reutrning const
> gchar* nd use nsAccessibleWrap::ReturnString() which keeps a static
> nsCString and returns a pointer into its buffer, and so requires caller of
> atk method to copy returned string before calling another atk function,
> which I think its very likely the bridge will always do.
I think I would try to avoid assumptions like this. Ginn?
(In reply to Trevor Saunders (:tbsaunde) from comment #22)
> or we could do what we do for a bunch of other atk methods reutrning const p::ReturnString () which keeps a static
> gchar* nd use nsAccessibleWra
> nsCString and returns a pointer into its buffer, and so requires caller of
> atk method to copy returned string before calling another atk function,
> which I think its very likely the bridge will always do.
I think I would try to avoid assumptions like this. Ginn?