[Development] Adding support for version number comparisons
oswald.buddenhagen at digia.com
Tue May 13 18:26:32 CEST 2014
On Tue, May 13, 2014 at 08:51:09AM -0700, Thiago Macieira wrote:
> Em ter 13 maio 2014, às 17:47:59, Oswald Buddenhagen escreveu:
> > the analogy is entirely bogus. the thresholds for usefulness and the
> > user's ability to manipulate the input into something the qt code can
> > work with are entirely different.
> We disagree.
how helpful. how about substantiating your opinion?
the user has complete control over the input of qversion, and can apply
any transformations which his use case may require. also, the effort
would be quite trivial (qstring::replace(qregexp())).
this contrasts at every level with cookie handling (in qnam?).
> > > QLibraryInfo is not about policy, either. It's just reporting what Qt's
> > > settings are.
> > it's reporting our installation directory layout policy. unfortunately,
> > that policy (which is basically FHS) doesn't match the ideal layout of
> > mac os bundles at all.
> QLibraryInfo is *reporting* what was configured. The policy / semantic decision
> was made at configure time. If we change the way we lay out our files by
> changing configure, QLibraryInfo will report it.
well, it seems you don't even understand why what we are doing is wrong.
bundles are supposed to be self-contained. this is *fundamentally*
incompatible with the shared per-type locations qt's directory layout
it's the perfect example for how putting policy into low-level classes
is risky business.
More information about the Development