Non-wrapped NX Open C functions

Non-wrapped NX Open C functions are Open C functions that have no .NET, Java, or Python bindings. Two reasons a function is left unwrapped:

1. The function has no meaningful use from .NET/Java/Python.
2. The C-side function signature/semantics are too complex to map cleanly.

The list is dominated by "free" helper functions (memory-release calls only relevant in C/C++, since wrapped languages rely on garbage collection instead) plus a handful of structurally complex APIs. Representative examples:

UF_ASSEM_free_deform_warnings_data
UF_ASSEM_free_prev16_aligns
UF_CLONE_free_validation_options
UF_CUT_LEVELS_free
UF_DRF_free_comp_data
UF_FAM_free_class_data
UF_FBM_GEOM_free_classified_set_list
UF_GDT_free
UF_KF_free_list_object_contents
UF_KF_free_rule_value
UF_LIB_free_rset_map
UF_MODL_free_bsurf_data
UF_MODL_free_compare_data
UF_MODL_free_compare_data_3
UF_MODL_free_law
UF_MODL_free_law_extension
UF_MODL_free_refit_face_feature_data
UF_MODL_free_rough_offset_data
UF_MODL_free_silhouette_flange
UF_MODL_free_snip_surface_feature_data
UF_MODL_free_string_list
UF_MODL_shape_pattern_free_cli...  (list continues, mostly UF_*_free_* helpers)

Takeaway: if you are calling one of these directly from C/C++ (Open C or Open C++), no wrapper equivalent exists in NX Open Common API — you must stay in Open C/C++ for that call, or route through a legacy interop bridge (see "Calling Legacy Open C from Common API Applications").

Related Topics

• Wrappers
• Open C functions used in NX Open methods