Knoll: Technical vision for Qt 6

afaik you can't really do it without a bunch of macros. I believe the qt people are thinking of replacing moc with reflection once that feature is available (probably 2023)

> He is speaking about weak/strong typing and you speak about dynamic typing, which is not the same thing.
The term strong/weak typing has been used inconsistently by different people, so it' not obvious at first what exactly Lars means when he writes about “strong typing”. But he does write this:

> A strong type system allows for IDEs and other tools to support our users in this task and dramatically ease the maintenance. Also, we will be able to generate much better-performing code and reduce overhead. […] With strong typing and simpler lookup rules we can convert QML to efficient C++ and native code

None of these make sense if you assume that by “strong typing” he means “absence of implicit conversions between types”, and they all make sense if you assume that what he really meant was static typing.

Dynamic typing in a programming language is just as bad, if not worse. Dynamic typing in (for example) Python, means some rarely called code can blow up at run time years after being put in production because a function is called with an object the function didn't expect. Not even 100% test coverage can help here. Another problem I see with dynamic typing is the lack of type declarations for variables and parameters. This makes it hard to read Python code, because there is no straightforward way to see what a function expects as parameters.

On the topic of weakly typed languages: sometimes I get the feeling C++ is a weakly typed language, not only because of the automatic conversions provided by the language, but also because coders spend way to much time to come up with esoteric explicit conversions and overloaded operators, just for the fun of it.