[Mono-devel-list] Weird warnings using mcs svn on Windows

Gert Driesen gert.driesen at telenet.be
Wed Apr 13 02:30:07 EDT 2005


> -----Original Message-----
> From: mono-devel-list-admin at lists.ximian.com 
> [mailto:mono-devel-list-admin at lists.ximian.com] On Behalf Of 
> Raja R Harinath
> Sent: woensdag 13 april 2005 8:21
> To: Gert Driesen
> Cc: mono-devel-list at lists.ximian.com
> Subject: Re: [Mono-devel-list] Weird warnings using mcs svn on Windows
> Hi,
> "Gert Driesen" <gert.driesen at telenet.be> writes:
> > As of recently, I get the following warning (numerous 
> times) when using mcs
> > svn to compile even the simplest app on Windows:
> >
> > warning CS8028: The method 'System.Object.Finalize()' is 
> marked 'override',
> > but
> > doesn't appear to override any virtual or abstract method: 
> it may be ignored
> > dur
> > ing overload resolution
> > C:\cygwin\usr\local\lib\mono\1.0\mscorlib.dll: 
> 'System.Object.Finalize'
> > (name of
> >  symbol related to previous warning
> >
> > Any idea what might be causing this ?
> A method is marked with the 'Virtual' MethodAttribute, but 
> doesn't have
> 'NewSlot' is treated as an "override" function.  The C# compiler tries
> to find the underlying "virtual" function that it overrides.  In some
> cases, it's unable to do so.  We can't get into this situation when
> compiling C# code.  So, this warning is typically issued when some dll
> was generated by SRE or written in IL.
> However, it turns out that several compiler-generated 
> functions are also
> being marked this way.  It's the case with a delegates .Invoke () on
> NET 1.1 and mono.
> I suspect that CSC 1.1 also emits the .Finalize () function this way,
> too.  I'll try to fix this soon.  However, I believe this warning is
> harmless in this case, since Finalize cannot be invoked such that it
> takes part in overload resolution.

I know, its just that I always tend to create build scripts in such a way
that it fails for any warning (meaning warninglevel 4, warnaserror set) ...

In this case its annoying, but definitely not a really big issue.

Thanks for looking into and (eventually) fixing this !


More information about the Mono-devel-list mailing list