http://mattdavid.net/2009/04/30/two-birds-with-one-stone/ Thu, 30 Apr 2009 12:54:29 +0000 hourly 1 http://wordpress.org/?v=3.0 http://mattdavid.net/2009/04/30/two-birds-with-one-stone/comment-page-1/#comment-11 matt Thu, 30 Apr 2009 12:54:29 +0000 http://mattdavid.net/2009/04/30/two-birds-with-one-stone/#comment-11 At least most of the SerialPort class is there. I remember the days before the SerialPort class was put in .net. Not so much fun. Actually, the code ends up being easier to read (IMO) without using the data events. So, I guess I shouldn't complain too much. At least most of the SerialPort class is there. I remember the days before the SerialPort class was put in .net. Not so much fun. Actually, the code ends up being easier to read (IMO) without using the data events. So, I guess I shouldn’t complain too much.

]]> http://mattdavid.net/2009/04/30/two-birds-with-one-stone/comment-page-1/#comment-10 SteveO Thu, 30 Apr 2009 11:24:20 +0000 http://mattdavid.net/2009/04/30/two-birds-with-one-stone/#comment-10 The SerialPort class does not notify when the hardware for which it is responsible generates an event? Sweet. That is clever, my friend. How else can you get code ported to a new platform quickly without omitting some ugly implementation details? The SerialPort class does not notify when the hardware for which it is responsible generates an event? Sweet. That is clever, my friend. How else can you get code ported to a new platform quickly without omitting some ugly implementation details?

]]>