Jump to content

  • Log In with Google      Sign In   
  • Create Account

Banner advertising on our site currently available from just $5!


1. Learn about the promo. 2. Sign up for GDNet+. 3. Set up your advert!


#Actualswiftcoder

Posted 18 June 2013 - 12:39 AM

I also think that starting to thread simple code is much easier than threading at the end where u can miss something and might have to debug... for a while : )

Or you could miss something, and end up having to debug from the start.
 
And by the way, debuggers don't really work in multithreaded code. Nor do log/print statements.
 
The only realistic way to approach multithreading is from a purely mathematical/theoretical standpoint.

Plus I am just doing this for fun to learn more about Java and graphics.

Multithreading has nothing to do with either Java or graphics. Nor "fun", for that matter.

#1swiftcoder

Posted 18 June 2013 - 12:38 AM


I also think that starting to thread simple code is much easier than threading at the end where u can miss something and might have to debug... for a while : )

Or you could miss something, and end up having to debug from the start.

 

And by the way, debuggers don't really work in multithreaded code. Nor do log/print statements.

 

The only realistic way to approach it is from a purely mathematical/theoretical standpoint.
 

Plus I am just doing this for fun to learn more about Java and graphics.

Multithreading has nothing to do with either Java or graphics. Nor "fun", for that matter.


PARTNERS