Quantcast

Maximum PC

It is currently Thu Oct 23, 2014 12:26 am

All times are UTC - 8 hours




Post new topic Reply to topic  [ 4 posts ] 
Author Message
 Post subject: Top 11 Compiler Warnings
PostPosted: Fri Jan 28, 2005 5:52 am 
8086
8086

Joined: Wed Aug 04, 2004 11:33 am
Posts: 82
Location: Hillsborough, NC
From BBSpot.com

11. WARNING: Only 5% of your current code will be portable to the Open Source version of .NET (code named Mono). This percentage will decrease even further with the next version of .NET. After all, you get what you pay for!

10. WARNING: Implementing your own Win32 message loop for a Windows Form really defeats the purpose of using .NET in the first place.

9. WARNING: Placing your own initials in a comment header at the top of each module you change may come back to haunt you. Instead, always use your boss' initials.

8. WARNING: Although C# allows code blocks to be marked as "unsafe", we call them "unsafe" for a reason. You appear to have ignored this subtle hint so we are taking this opportunity to warn you a second time.

7. WARNING: You appear to have marked your entire application as "unsafe". You may want to consider printing a consumer warning label on your software packaging. As a side note, nobody ever reads the Licensing Agreement so a more visible location may offer better legal protection.

6. WARNING: Declaring variables as "Int32" everywhere instead of "int" is just plain annoying. Please stop it.

5. WARNING: Although the use of the Internet Explorer Web Browser control is currently the only way to show HTML content on a Windows Form, its use is not recommended. Do we really need to say why?

4. WARNING: Despite the fact that most programming books leave it out, structured error handling is considered to be a good programming practice.

3. WARNING: Drag and drop database programming using the data components is only intended for newbies writing trivial applications. A project containing 400,000+ lines of code is not considered trivial. Please consider implementing an actual data layer in your project.

2. WARNING: Please do not contact Technical Support about this warning. Instead, send all correspondence to TimWigglenuts@Microsoft.com. Adding this warning was his brilliant idea.

1. WARNING: TimWigglenuts@Microsoft.com is not a valid email address. All spam sent to this email address will be forwarded to TimBiggernuts@Microcrotch.com.


Top
  Profile  
 
 Post subject: Re: Top 11 Compiler Warnings
PostPosted: Sun Jan 30, 2005 3:51 am 
Thunderbird
Thunderbird
User avatar

Joined: Wed Jul 07, 2004 1:13 pm
Posts: 817
Location: Missouri
fitbabits wrote:
From BBSpot.com

11. WARNING: Only 5% of your current code will be portable to the Open Source version of .NET (code named Mono). This percentage will decrease even further with the next version of .NET. After all, you get what you pay for!

10. WARNING: Implementing your own Win32 message loop for a Windows Form really defeats the purpose of using .NET in the first place.

9. WARNING: Placing your own initials in a comment header at the top of each module you change may come back to haunt you. Instead, always use your boss' initials.

8. WARNING: Although C# allows code blocks to be marked as "unsafe", we call them "unsafe" for a reason. You appear to have ignored this subtle hint so we are taking this opportunity to warn you a second time.

7. WARNING: You appear to have marked your entire application as "unsafe". You may want to consider printing a consumer warning label on your software packaging. As a side note, nobody ever reads the Licensing Agreement so a more visible location may offer better legal protection.

6. WARNING: Declaring variables as "Int32" everywhere instead of "int" is just plain annoying. Please stop it.

5. WARNING: Although the use of the Internet Explorer Web Browser control is currently the only way to show HTML content on a Windows Form, its use is not recommended. Do we really need to say why?

4. WARNING: Despite the fact that most programming books leave it out, structured error handling is considered to be a good programming practice.

3. WARNING: Drag and drop database programming using the data components is only intended for newbies writing trivial applications. A project containing 400,000+ lines of code is not considered trivial. Please consider implementing an actual data layer in your project.

2. WARNING: Please do not contact Technical Support about this warning. Instead, send all correspondence to TimWigglenuts@Microsoft.com. Adding this warning was his brilliant idea.

1. WARNING: TimWigglenuts@Microsoft.com is not a valid email address. All spam sent to this email address will be forwarded to TimBiggernuts@Microcrotch.com.


For this I will just have to delve into my little collection of Java compile errors and website I have collected. I will post it ASAP.


Top
  Profile  
 
 Post subject:
PostPosted: Sun Feb 20, 2005 5:54 pm 
Thoroughbred
Thoroughbred
User avatar

Joined: Mon Jan 24, 2005 2:05 pm
Posts: 1739
Location: howell, mi
LOL

Edit

I should elaborate on what I said. The rules that where posted made me laugh, thus I wrote LOL. If you need more of and explanation please contact me. Thank you for your time.


Top
  Profile  
 
 Post subject:
PostPosted: Tue Mar 01, 2005 12:44 pm 
SON OF A GUN
SON OF A GUN
User avatar

Joined: Mon Nov 01, 2004 5:41 am
Posts: 11605
My favorite error while compiling against the gcc compiler:

"Confused by earlier errors, bailing out."


Top
  Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 

All times are UTC - 8 hours


Who is online

Users browsing this forum: No registered users and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group

© 2014 Future US, Inc. All rights reserved.