Comments for The .Net frog

Comment on Choosing composition over inheritance: yet another example! by Sri

Sri — Thu, 08 Mar 2012 05:35:39 +0000

Nice explanation.

Comment on Choosing composition over inheritance: yet another example! by bibin

bibin — Mon, 06 Feb 2012 06:10:41 +0000

Well done explained with great ease..

Comment on lock(this): don’t! by lock

lock — Wed, 01 Feb 2012 11:07:06 +0000

lock

Comment on lock(this): don’t! by Anonymous

Anonymous — Fri, 06 Jan 2012 12:45:57 +0000

alert(‘hello’)

Comment on Choosing composition over inheritance: yet another example! by Abhi

Abhi — Tue, 13 Dec 2011 11:04:42 +0000

Well done

Comment on AutoResetEvent vs ManualResetEvent: beware! by josef

josef — Wed, 03 Aug 2011 18:16:18 +0000

one more important difference to mark:

An autoreset event can only unblock one waitfor…object call. As the event will be reset by the first waitfor..object. Other waitfor…object loops will NOT unblock!

The manual reset event unblocks ALL waiting calls of waitfor…objects! The sender should then reset the event automatically.

regards

Josef

Comment on AutoResetEvent vs ManualResetEvent: beware! by sandeep

sandeep — Wed, 20 Jul 2011 19:53:15 +0000

Well the name itself say.. AutoReset and ManualReset…

Comment on Choosing composition over inheritance: yet another example! by Sunil Raskar

Sunil Raskar — Fri, 17 Jun 2011 08:14:06 +0000

In trip or tripbase class, the _from or _to properties are declared as read only and it has been assigned a value in non default contractors. It should be not read only if values are require to assigned.

Comment on Performance impact of the readonly keyword by ?????? ????

?????? ???? — Wed, 01 Jun 2011 18:12:24 +0000

xzsd

Comment on AutoResetEvent vs ManualResetEvent: beware! by Siva Koganti

Siva Koganti — Wed, 15 Dec 2010 19:05:03 +0000

Very good point elevated. Thanks!

Comment on AutoResetEvent vs ManualResetEvent: beware! by Rick O'Shay

Rick O'Shay — Thu, 19 Aug 2010 21:47:49 +0000

So, AutoResetEvent automatically resets while ManualResetEvent requires a manual reset. Reminds me of the time I scaled myself drinking what I thought was a cool drink of water. Turns out the tap labeled “hot” had hot water, I should have used the tap labeled “cold”.

Comment on Performance impact of the readonly keyword by Andrei Rinea

Andrei Rinea — Wed, 17 Mar 2010 08:38:54 +0000

Maybe your co-worker was confusing readonly with const.

That would make a lot of sense..

Comment on AutoResetEvent vs ManualResetEvent: beware! by ???????? ????

???????? ???? — Wed, 06 Jan 2010 15:07:18 +0000

Just imagine that the AutoResetEvent executes WaitOne() and Reset() as a single atomic operation.
thanks for the great article!

Comment on Choosing composition over inheritance: yet another example! by ??????

?????? — Wed, 21 Oct 2009 13:25:58 +0000

???? ??? ?????

Comment on AutoResetEvent vs ManualResetEvent: beware! by Anonymous

Anonymous — Fri, 18 Sep 2009 13:33:00 +0000

If AutoresetEvent’s Set is Called when it is not required, then there is no use of Waitone in the thread.. Beaware of it folks !!!

Comment on AutoResetEvent vs ManualResetEvent: beware! by Anonymous

Anonymous — Fri, 18 Sep 2009 13:31:50 +0000

Yes u r right.. but there is one more problem here in AutoresetEvent’s
Set Method.. It has to be called when it is needed. if not again u will get into trouble.

Comment on Choosing composition over inheritance: yet another example! by Naveena

Naveena — Wed, 01 Apr 2009 22:04:44 +0000

Simple example.. thanks

Comment on Choosing composition over inheritance: yet another example! by Anonymous

Anonymous — Wed, 01 Apr 2009 22:04:09 +0000

Excellent

Comment on Choosing composition over inheritance: yet another example! by Julien

Julien — Fri, 13 Mar 2009 06:41:54 +0000

It certainly was, my apologies !
I’ll fix it right now !

Comment on Choosing composition over inheritance: yet another example! by brad

brad — Thu, 12 Mar 2009 15:03:07 +0000

That’s what I thought, but the trip constructor that takes three arguments is assigned protected not public. If I change your example to public, it works fine. Was protected a mistype?