You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When dealing with objects of type BipElt or BipFunction, we have the is_user_name property.
However, when working with objects of type HxLvar, the semantically identical property is called has_user_name instead.
In addition, BipElt and BipFunction provide some useful utility methods such as is_ida_name, is_dummy_name, etc. that are not exposed for HxLvar objects.
Is it possible to create a more consistent API between objects of different types?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi,
When dealing with objects of type
BipElt
orBipFunction
, we have theis_user_name
property.However, when working with objects of type
HxLvar
, the semantically identical property is calledhas_user_name
instead.In addition,
BipElt
andBipFunction
provide some useful utility methods such asis_ida_name
,is_dummy_name
, etc. that are not exposed forHxLvar
objects.Is it possible to create a more consistent API between objects of different types?
Thanks!
The text was updated successfully, but these errors were encountered: