Skip to content

More consistent API between objects of different types #25

@assafcarlsbad

Description

@assafcarlsbad

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions