synacktiv / bip

BSD 3-Clause "New" or "Revised" License
189 stars 19 forks source link

More consistent API between objects of different types #25

Open assafcarlsbad opened 2 years ago

assafcarlsbad commented 2 years ago

Hi,

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!