Welcome to DU! The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards. Join the community: Create a free account Support DU (and get rid of ads!): Become a Star Member Latest Breaking News Editorials & Other Articles General Discussion The DU Lounge All Forums Issue Forums Culture Forums Alliance Forums Region Forums Support Forums Help & Search

Website, DB, & Software Developers

DaveJ

(5,023 posts)

4. I'm using C#/.Net

Reply to Recursion (Reply #1)

Mon Jun 17, 2013, 09:13 AM

Jun 2013

I still don't understand why there is any concern that a value will overwrite another value, unless the code is sharing a variable among threads. I would think that this would be well documented or handled by .Net if there were a constant danger of variables overwriting one another.

Edit history

Please sign in to view edit histories.

Recommendations

0 members have recommended this reply (displayed in chronological order):

9 replies

= new reply since forum marked as read

Highlight:

Do I need to worry about thread safe methods? [View all] DaveJ Jun 2013 OP

Any function that keeps an internal state needs thread safety Recursion Jun 2013 #1

I'm using C#/.Net DaveJ Jun 2013 #4

This is the importance of the static keyword Recursion Jun 2013 #7

This is exactly why you need to think about it. ManiacJoe Jun 2013 #9

Just because you don't create a thread doesn't mean they aren't created. jeff47 Jun 2013 #2

I'm aware that threads are created since there are multiple users DaveJ Jun 2013 #5

Pretty much any web platform will come with a good degree of thread safety. napoleon_in_rags Jun 2013 #3

I agree. DaveJ Jun 2013 #6

Maybe its your boss's love of static methods. napoleon_in_rags Jun 2013 #8