Jump to content

View more

Image of the Day

雑魚は多めにして、爽快感重視にしつつ・・・(´・ω・`)
早いとこ、ベースを作って、完成にもっていかないとね。
タイトルもまだ迷ってるだよなぁ。 
#indiedev  #indiegame #screenshotsaturday https://t.co/IwVbswGrhe
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.


Sign up now

Start cringing: Some guy might be getting his worst day cut out for him.

4: Adsense

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.


  • You cannot reply to this topic
9 replies to this topic

#1 asperatology   Members   

693

Posted 12 September 2012 - 07:46 AM

Came from FB news feed. No back story though... I mis-copy/paste the title.

Posted Image

#2 slicer4ever   GDNet+   

Posted 12 September 2012 - 08:19 AM

it can be common for a large project to generate such a large number of errors if someone forgets even a semi-colon, or to close a bracket, which is most likely the case.

Edited by slicer4ever, 12 September 2012 - 08:19 AM.

Check out https://www.facebook.com/LiquidGames for some great games made by me on the Playstation Mobile market.

#3 FLeBlanc   Members   

Posted 12 September 2012 - 09:05 AM

My general rule of thumb is to ignore every error but the first one (or maybe the first couple, if a quick scan suggests they might stem from different causes). Errors in compilation tend to cascade, just as slicer4ever suggests, so a huge error list isn't exactly accurate information.

The warning list, too, might not be accurate since a warning generated in a header that is included multiple times will generate multiple warnings, and often you can eliminate a huge piece of your warning list just by fixing that one header.

Edited by FLeBlanc, 12 September 2012 - 09:08 AM.


#4 asperatology   Members   

693

Posted 12 September 2012 - 09:35 AM

I agree with all of the above. We couldn't really tell just by looking at the error and warning counts.

Overall, it's a nice humor. :D

#5 alnite   Members   

Posted 12 September 2012 - 05:26 PM

With today's IDE with syntax highlighting and intellisense, I'm surprised that somebody are still making compile-time errors.

My intellisense-sense would start tingling as soon as nothing comes up when I expected it to come up.

#6 tstrimple   Prime Members   

Posted 12 September 2012 - 05:28 PM

It's most likely just missing references. It always looks a little scary when you build with a missing reference. Those errors add up very fast.

#7 way2lazy2care   Members   

786

Posted 12 September 2012 - 05:40 PM

With today's IDE with syntax highlighting and intellisense, I'm surprised that somebody are still making compile-time errors.

My intellisense-sense would start tingling as soon as nothing comes up when I expected it to come up.

On a handful of projects I've been on I've turned off intellisense because it can be a real resource hog on some larger projects with atypical build processes.

#8 Koobazaur   Members   

Posted 13 September 2012 - 10:54 PM

It's most likely just missing references. It always looks a little scary when you build with a missing reference. Those errors add up very fast.


Ugh, aye, I hate it with C++ and headers when you make an error, and it gets reproted like 50 times because the file is included 50 times. Really VS? Can't you figure out it and group them already???

(that's on VS2008, mebbe 2010 already fixed that)
Comrade, Listen! The Glorious Commonwealth's first Airship has been compromised! Who is the saboteur? Who can be saved? Uncover what the passengers are hiding and write the grisly conclusion of its final hours in an open-ended, player-driven adventure. Dziekujemy! -- Karaski: What Goes Up...

#9 d000hg   Members   

Posted 15 September 2012 - 07:00 AM

My Ogre build on the Mac gives 5-15k warnings in Xcode, all about visibility being changed or something. Not sure why and I don't really get XCode enough to care as long as the Mac port of my code runs. Ugh, Xcode's just foul after VC++.

#10 SymLinked   Members   

Posted 15 September 2012 - 08:22 AM

With today's IDE with syntax highlighting and intellisense, I'm surprised that somebody are still making compile-time errors.

My intellisense-sense would start tingling as soon as nothing comes up when I expected it to come up.


Yeah, because intellisense (especially pre-2010) is known to work all the time and not delay itself for several minutes on non-trivial projects.




Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.