Transform a QVector / QStringList in a va_list

[amleto]

lol, second time in two days I see a C lover call C++ ugly! C++ is much prettier than C imo. va_list is inherently unsafe as there is no type checking, so you should not worry about the same issue in your macros. Generally this is a problem throughout C! Your PM sounds like a douche. If you are using Qt, then there is already a C++ 'bottleneck', so why stick to C?

The best way is to expose

void messagebox(json_object **json, char *iconType, char *title, char *msg, int showTime, va_list ap)

void messagebox(json_object **json, char *iconType, char *title, char *msg, int showTime, va_list ap)

To copy to clipboard, switch view to plain text mode 

so that you can make your own va_list and pass into this method. Without this available, you only have hack solutions, I think.

[fanoI]

lol, second time in two days I see a C lover call C++ ugly! C++ is much prettier than C imo. va_list is inherently unsafe as there is no type checking, so you should not worry about the same issue in your macros. Generally this is a problem throughout C! Your PM sounds like a douche. If you are using Qt, then there is already a C++ 'bottleneck', so why stick to C?

I think in the same way C++ is better than C overloading, inheritance, GUI toolkits (as our friend Qt), event driven programming... the only thing that C++ did wrong is, IMHO, that could be, for someone, one of its point of force the C compatibility why:

1. All the pointers things are unsafe!
2. The C compatibly is not complete, too... an essential C keyword called NULL is not present (it calls it "0"), and an empty variable doesn't evaluates to false
3. Code that C compiles perfectly or giving only a warning doesn't compile in C++ !

We maybe you could hate me but I, personally, prefer the Java approach all is object (well not completely to be honest int is primitive variable Int is the object), no pointer and no compatibility with the old, ugly (it is that beast that is ugly not Qt/C++) and unsafe C.

By the way yes va_args are unsafe __builtin_va_arg_pack() tries to mitigate the problem as at least permits to check the size of the args without the need to use a variable or a NULL in the end but yes if I pass an int instead of char * the code would compile and, probably will crash when it will try to convert to a char *!

In the end if I don't have done nothing wrong and there's a bug in __builtin_va_arg_pack() when called by a function that calls again __builtin_va_arg_pack() I go for a hibryd approach: I'll implement the info(), warning(), alert(), wait() as variadic macro that will call the messagebox function... but I hate the macro syntax in particular when I have to write functions like macros

The best way is to expose

void messagebox(json_object **json, char *iconType, char *title, char *msg, int showTime, va_list ap)

void messagebox(json_object **json, char *iconType, char *title, char *msg, int showTime, va_list ap)

To copy to clipboard, switch view to plain text mode 

so that you can make your own va_list and pass into this method. Without this available, you only have hack solutions, I think.

By the way the hack is in test code so not problem but the curiosity remains is possible to use the Meta Object Compiler to create your own code?
I could use him to make a switch for example? Maybe in the future I could find a good usage of this technique...

[amleto]

what would be the point in using moc to generate code? your problem is still a run-time problem, so moc can't help you there...

[fanoI]

See my fist post I wanted MOC to help me to write at least the first 32 version of the switch()... is this possible?

It is in general possible to make MOC create custom code?

[amleto]

no, I don't think so. Just write it by hand - it's going to look ugly whether you do it or moc does it (if it could).