> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/9.0/developer-guide/idc/idc-api-reference/alphabetical-list-of-idc-functions/1741.md).

# Local types information and manipulation helpers

```
// Enum type information
class enum_type_data_t
{
  // tattr_enum, see TAENUM_... flags
  attribute taenum_bits;

  // enum member sizes (shift amount) and style, see BTE_... constants
  attribute bte;

  // number of enum members
  attribute member_cnt;

  // add enum constant
  success add_constant(string name, string name, uint64 value, string comment=nullptr);
};
```

// Get named local type TID // name - type name // returns: TID or BADADDR long get\_named\_type\_tid(string name);

// Get numbered local type TID // ord - type ordinal // returns: TID or BADADDR long get\_numbered\_type\_tid(long ord);

// create type enum // enum\_name - type name // ei - enum type data of type enum\_type\_data\_t // enum\_width - the width of a enum element, allowed values: 0 (unspecified),1,2,4,8 // sign - enum signess (any from TYPE\_SIGN\_... constants) // convert\_to\_bitmask - try convert enum to bitmask enum (0-false or 1-true) // enum\_cmt - enum type comment // returns: enum TID long create\_enum\_type( string enum\_name, object ei, long enum\_width, long sign, long convert\_to\_bitmask, string enum\_cmt=nullptr); // type signedness #define TYPE\_SIGN\_NO\_SIGN 0 // no sign, or unknown #define TYPE\_SIGN\_TYPE\_SIGNED 1 // signed type #define TYPE\_SIGN\_TYPE\_UNSIGNED 2 // unsigned type


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hex-rays.com/9.0/developer-guide/idc/idc-api-reference/alphabetical-list-of-idc-functions/1741.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.