Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / Managed C++ / April 2004

Tip: Looking for answers? Try searching our database.

Warnings-as-errors, /Wp64

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Bern McCarty - 26 Apr 2004 20:24 GMT
We have a large source base that we normally compile with /WX (treat all
warnings as errors) and /W3.  I would like to add the /Wp64 switch to this
mix so that developers see the /Wp64 warnings but I don't want them to be
treated as errors.  Treating them as errors would be impossible at this
point since there will be tons of them.  At this point my aim is to build
awareness and at least get developers that are writing a lot of new code to
write it so that it is 64-bit clean.

Is there an easy way to do what I want to do?

-Bern
Gary Chang - 27 Apr 2004 11:47 GMT
Hi Bern,

You want to mixed the /WX with the /Wp64, and exclude the /Wp64 warning
from the other warnings which treated as errors.

It seems... tough, I will consult this issue with the dev team member to
see is there a workaround for you to achieve that.

Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Online Partner Support

Signature

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
Gary Chang - 28 Apr 2004 03:05 GMT
Hi Bern,

Unfortunately, it appears impossible to exclude /Wp64 warnings from the /WX
warnings(errors).

However, one member of the dev team suggest:

"#pragma warning(error: ####)

where #### is replaced by the complete list of warnings that they care
about.  Then, stop using /WX in the builds.

(Maybe you could extend #pragma warning (and the matching cmd line
switches) to allow specifying a warning level for an entire class of
warnings:  #pragma warning(error: W1 W2 W3) for example...)
"

Thanks!

Best regards,

Gary Chang
Microsoft Online Partner Support

Signature

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.