slots is a reserved keyword on qt about spine-runtimes HOT 11 CLOSED

Namespaces.

from spine-runtimes.

It's not SlotData that is the problem it is the variable name slots in the class definition?

Maybe I misunderstand what your saying. Sorry

from spine-runtimes.

Oh right, so it's not a scope thing?

from spine-runtimes.

No its not.
It's used like this.

class bla{

public:
int hi;

private:
int bye;

public slots:
void setValue(int value);

signals:
void valueChanged(int newValue);
}

so the words slots and signals are reserved and we cant use them as a variable name in a class.

from spine-runtimes.

Note this only affects headers, as C files should not be fed to QT moc. Still, it's bloody annoying.

from spine-runtimes.

What version of QT are you using? QT 4+ has QT_NO_KEYWORDS, then you use Q_SIGNALS and Q_SLOTS instead of signals and slots in your programs. Is this acceptable? Slots are called slots in Spine, I'm not keen on changing the names in Spine code.

For a QT 3 and below workaround, we could undef slots, described here:
http://lists.trolltech.com/qt-interest/2008-01/thread00347-0.html
I'd rather keep QT specific stuff out of Spine code. You could surround all Spine header #includes in your code with the undef.

from spine-runtimes.

I'm using QT 5.0.2.
I'm building libspine separate and then when its a static library trying to link it into my cocos/qt project.
So yes its only when we include the headers in qt and is quite annoying.

I didn't even know qt3 was still supported.
Don't think anyone uses that anymore and I'd agree completely on keeping qt specific code out of spine.

I have no problem using QT_NO_KEYWORDS.
I'll test it there now and see if it works.

Thanks for the reply :)
I'll be back asap

from spine-runtimes.

It works but I must use Q_FOREACH instead of foreach also.
Do you want to make a wiki page on this for others?

from spine-runtimes.

Glad that works! I will document use with QT when I write docs for the C runtime.

from spine-runtimes.

👍 Thanks dude

from spine-runtimes.

I tried to use ECL (a common lisp) and the reserved keyword slots spoils the whole idea I had:

In ecls object.h

struct ecl_instance {           /*  instance header  */
        _ECL_HDR1(isgf);
        cl_index length;        /*  instance length  */
        cl_object clas;         /*  instance class  */
        cl_objectfn entry;      /*  entry address  */
        cl_object sig;          /*  generation signature  */
        cl_object *slots;       /*  instance slots  */
};

So what again is an easy way to work around this?

from spine-runtimes.