# Hxcpp: option to not append \_obj to class names?

**URL:** https://community.haxe.org/t/hxcpp-option-to-not-append-obj-to-class-names/2506
**Category:** Haxe
**Created:** [June 5, 2020, 2:11am UTC](https://community.haxe.org/t/hxcpp-option-to-not-append-obj-to-class-names/2506 "2020-06-05T02:11:38Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![ibilon](https://community.haxe.org/user_avatar/community.haxe.org/ibilon/32/13_2.png) [@ibilon](https://community.haxe.org/u/ibilon)
#### Post date: [June 5, 2020, 11:35am UTC](https://community.haxe.org/t/hxcpp-option-to-not-append-obj-to-class-names/2506/2 "2020-06-05T11:35:22Z")

</div>

The hxcpp output isn’t very idiomatic, because c++ and haxe don’t have the same semantics on many things.

It isn’t just about the `_obj` suffix, if also doesn’t use `new` since you need a GC allocation, and in haxe you don’t have to call the super constructor as the first instruction in a constructor, but c++ does.

Arrays are pretty special and need casting and possibly boxing for the elements.

The GC needs to be init and called.

I wouldn’t recommend using hxcpp to create a c++ library.

---

_[View the full topic](https://community.haxe.org/t/hxcpp-option-to-not-append-obj-to-class-names/2506)._