compiler message cannot convert GType to GType
Brad Roberts
braddr at puremagic.com
Sun Mar 12 21:05:07 PST 2006
On Sun, 12 Mar 2006, Ant wrote:
> Brad Roberts wrote:
> > On Sun, 12 Mar 2006, Ant wrote:
> >
> > > Ant wrote:
> > > > gobject/ObjectG.d(389): cannot implicitly convert expression
> > > > (objectType) of
> > > > type GType to GType
> > > >
> > > > All unhelpful compiler message should be marked as high priority bugs.
> > > > this one is just an example
> > > >
> > > > Ant
> > > Walter, I didn't realized it until now but, as 2 years ago,
> > > I'm spending as much time fighting dmd as I am actually using it... :(
> > >
> > > hey, but I'm still using it, I didn't go back to c++ ;)
> > >
> > > Ant
> >
> > Produce a test case that doesn't involve having to download packages and
> > examine hundreds or thousands of lines of code, and chances are the problem
> > _will_ be fixed. In this case, you've neither given any indication of what
> > the code actually is, where/how to get it, or how to reproduce the problem.
>
> that was not my intention, I just want to say that Walter should change
> the priority he is given to dumb compiler message.
>
> (You could question my choice of posting on the bugs group.)
>
> Ant
I don't question posting in .bugs at all. It's entirely appropriate as
bad error messages are a big part of the usability of the compiler. Maybe
not as blocking as a crash, but still worth fixing.
My point is that like any problem report, to be useful it needs to be
trivially reproducable. That holds for warnings, errors, crashes,
whatever. Just showing the line of output by itself is insufficient in
most cases. So, to facilitate getting these issues fixed, tiny test cases
would be invaluable.
Later,
Brad
More information about the Digitalmars-d-bugs
mailing list