Thread.Sleep...

[news.microsoft.com]

Normally for using collections one uses the provided .SynRoot property thats
there for that task. If you look at the examples for IEnumerable on
collecitons thats what it uses. collectionObj.SynRoot

Still, I like to keep locks to a minimum and I dont see a need for a lock
there on an already synchronized object so AutoResetEvents seemed to me to
be more appropriate.

Being a win32 coder , AutoResetEvents makes more sense to me as you point
out.

 

[Curious]

To Alvin.

What's up with u dude - are you just a part-time ass or what? I
noticed ur stupid post towards someone who asked a question regarding
NGEN in one of the other .NET groups, as well as the rubbish ur
posting to Jon Skeet in this thread.

If you have something funny to say, then say it. If you have sod all
useful to say - look into a mirror and tell it to the only person who
cares.

I've seen other posts by you where you have actually helped a lot of
people, why do you then insist on posting crap at other times? There's
always one I guess.......

 

[Jon Skeet [C# MVP]]

Normally for using collections one uses the provided .SynRoot property thats
there for that task. If you look at the examples for IEnumerable on
collecitons thats what it uses. collectionObj.SynRoot

Yes, SyncRoot is fine for that purpose, but it's often nice to have
separate monitors specifically for thread waiting/notification. It just
makes life a bit easier to understand (IMO) and threading is a very
hard thing to get right to start with.

Still, I like to keep locks to a minimum and I dont see a need for a lock
there on an already synchronized object so AutoResetEvents seemed to me to
be more appropriate.

Being a win32 coder , AutoResetEvents makes more sense to me as you point
out.

You should be aware that AutoResetEvents almost certainly use their own
locks internally - I'd be very surprised if they were actually
significantly more efficient than using Monitor.Wait/Pulse. I'm not
saying you shouldn't use them - it's a matter of personal preference,
as I've said, and your last reason makes a lot of sense, but I wouldn't
focus too much on not having many locks. Making sure that you only lock
what you need to is more important, and that usually involves having
*more* locks available, to make each one finer-grained.

 

[Alvin Bruney]

NGEN? Can you post this so called thread so I can take a look at it.

NGEN in one of the other .NET groups, as well as the rubbish ur
posting to Jon Skeet in this thread.

What gives you the right to jump in here and declare it was rubbish? I have
solid reasons for posting a question like this. May be you should ask before
taking a shot eh?

My reason for posting this

it is just soooo discouraging, that's all.

was because I am feeling rather inadequate with my thread knowledge. I was
simply wanting to know if I needed to keep working in the pursuit of
increasing this knowledge or whether I should give it up and do something
else with my life. As he said, it took him a while to get there. I'm not
there yet. That is why it is discouraging to me. I wasn't going to reply to
your bullshit because I didn't think I was being a half ass. You could have
just asked instead of jumping the gun.

And by the way, an individual calling himself Jack Mayoff has been spoofing
my email account (and others by the way) replying to threads in my name. I
haven't caught all his attempts but you may be referring to one of his. I
wont give you the benefit of the doubt either. In short, if you follow my
post, it is rather easy to differentiate between me and a wanna be. But then
again, you couldn't get this last one so go figure.

shall we say an apology is in order? preach, do you think i was being a half
ass?

 

[news.microsoft.com]

NGEN? Can you post this so called thread so I can take a look at it.


What gives you the right to jump in here and declare it was rubbish? I have
solid reasons for posting a question like this. May be you should ask before
taking a shot eh?

I have solid crap in my toilet.

My reason for posting this


was because I am feeling rather inadequate with my thread knowledge. I was
simply wanting to know if I needed to keep working in the pursuit of
increasing this knowledge or whether I should give it up and do something
else with my life. As he said, it took him a while to get there. I'm not
there yet. That is why it is discouraging to me. I wasn't going to reply to
your bullshit because I didn't think I was being a half ass. You could have
just asked instead of jumping the gun.

And by the way, an individual calling himself Jack Mayoff has been spoofing
my email account (and others by the way) replying to threads in my name. I
haven't caught all his attempts but you may be referring to one of his. I
wont give you the benefit of the doubt either. In short, if you follow my
post, it is rather easy to differentiate between me and a wanna be. But then
again, you couldn't get this last one so go figure.

shall we say an apology is in order? preach, do you think i was being a half
ass?

No I don't think you were being a "half ass" I think you area a "complete
ass".

 

[Curious]

Yo.

Ahhh, well in that case it seems that indeed I was in the wrong. I
guess it was one of those days and I needed to get some steam out.

Having read some of your earlier posts and then reading "your" reply
to:

NGEN microsoft system dlls? by Bob Whiton in
microsoft.public.dotnet.performance

I thought hang on, that's a bit out of order.

Again, appologies for jumping the gun there - never meant to upset you
in any way. I would feel bad if I did annoy you.

All the best dude.

'The mistakes of others are good teachers'. Proverb.

 

[Alvin Bruney]

It's all good. No hard feelings.