Weird issue with inheritance tree (LB3 only) about luabridge3 HOT 6 CLOSED

This is quite severe and i'm surprise there isn't a unit test for it. Will investigate

from luabridge3.

I'm guessing it's because of the new LB3 hashing of classnames.

from luabridge3.

Are thos your effective class names ? Can you provide me the real names ?

from luabridge3.

I am away from my dev box at the moment, but here is a skeleton version off the top of my head:

class __FCBase {};
class __FCBaseData : public __FCBase {};
class __FCOther : public __FCBaseData {};
class __FCInciOther : public __FCOther {};
class __FCNoInciOther : public __FCOther {};
class FCStaffSystem : public __FCNoInciOther {}; // this is the problem class
class FCSystemStaff : public __FCInciOther {}: // possible hash conflict?

If you need to fill it in further, the full class hierarchy is explorable here. There are other classnames in the hierarchy that might fool a hash, such as FCSystemStaff and FCStaffSystems. In fact, if I had to put money on the one that is the problem, it would be FCSystemStaff (same letters, different order.) I added it above.

from luabridge3.

There was indeed a bug in the class name hashing. Pretty bad, sorry for the issue. Will be merged shortly.

from luabridge3.

I can confirm that your modification for this fixes my issue.

Many thanks.

from luabridge3.