>   4494  /*
>   4495      generated by moc
>   4496  */
>   4497  template<>
>   4498  struct connect<ProtectedSignal>
> 
> You need to move this struct to the header, which means either boilerplate
> code written by the developer or an include of a moc-generated file in a
> public header. Both options would suck IMHO.
> 

Thinking about your "this sucks" I came to a other conclusion:

With Qt5 it is possible to introduce new features which make
things possible which are impossible with Qt4.
And such a new feature would be moc-generated headers.

I know, most C++-purists don't like it, and at the moment there
is the idea to make Qt5 more C++/std-only. But Qt will always 
need the moc preprocessor, and this is because of the lack of
some features in C++.

C++ is a multi-paradigm programming language, and moc only adds
another paradigm. So why not introducing more code-generation by 
supporting moc-generated headers? I'm sure this will simplify
things in future, and makes new things possible, because with the 
C-preprocessor and templates not all ideas could be implemented.

Peter



-- 
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
_______________________________________________
Qt5-feedback mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback

Reply via email to