Andrés G. Aragoneses wrote: > Nicola Dell'Amico escribió: >> Chris Howie wrote: >>> On Feb 20, 2008 3:07 PM, Robert Jordan <[EMAIL PROTECTED]> wrote: >>>> Nicola Dell'Amico wrote: >>>>> Sadly , Monodevelop 0.18 doesn't report any error into the Error List !! >>>>> while in Build Output the exception output was shown: I had hard time >>>>> figuring out my code was faulty ! >>>> It makes absolutely no sense to mix compiler exceptions with your own >>>> syntax errors in the same list. >>>> >>>> The build output exists for a reason: to look at it when something >>>> went wrong. It's your own fault if you didn't. >>> If I read the original message correctly, the point is that there is a >>> CS#### message for this error but instead of reporting it properly mcs >>> just explodes. >>> >> Yes, you are right Chris. >> I don't care about Monodevelop, the post was about an exception >> improperly thrown by mcs instead of detecting a switch duplicate case >> error. That's all ... >> >> Anyway, IMHO, I think Monodevelop shouldn't report 'Build successful' >> when mcs throws an exception... but I have no interest on further >> investigating on that. > > I think you should file two bugs: > - One with the testcase that made mcs explode. > - One requesting that mcs/gmcs doesn't report 0 errors if it has found > an exception while parsing. > > Regards, > > Andrés [ knocte ] > I think I'll file only the first one bug. When mcs throws an exception it doesn't report 0 errors ... just stops parsing showing the caught exception text. I think is up to the tool (i.e. Monodevelop or which other else ) calling mcs to properly parse the mcs's output.
Regards Nicola -- http://www.ndatech.it _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
