[Kde-bindings] A sample of our subset of QtC

[Richard Dale]

On Saturday 11 January 2003 7:48 pm, Ashley Winters wrote:
> --- Richard Dale <Richard_Dale at tipitina.demon.co.uk> wrote:
> Also, it's rather unpleasant to have the possibility of function "ids"
> changing between versions. If you're gonna tack an effectively random
> number on the end of every function, why not go all the way like smoke
> does? f1, f2, ..., f4897.
I think the idea was to always generate the QtC bindings at the same time as 
the bindings that call them, and with the same tool - so the function names 
would be in sync. I got the simple naming scheme from the mark 1 version of 
QtC by Roberto Alsina.

> I'd propose using a standard name-mangling scheme for the arguments.
>
> QApplication(const char **, int)
> QApplication_cCPP_i  (char CONST POINTER POINTER, int)
>
> It would be possible to document a mapping from "mangled" names to
> "easy" names that way. qtc_QApplication() would always call
> QApplication_cCPP_i or something
Is this the same as the name mangling that gcc uses?

-- Richard