tag:blogger.com,1999:blog-29331675.post2016952622960763389..comments2024-03-05T17:37:00.995+01:00Comments on The Delphi Geek: OmniThreadLibrary Example #3: Bidirectional communicationgabr42http://www.blogger.com/profile/06903558857617342477noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-29331675.post-16765869166215830952008-07-03T11:26:00.000+02:002008-07-03T11:26:00.000+02:00@anonymous:- Yes, I totally agree. I'll probably c...@anonymous:<BR/><BR/>- Yes, I totally agree. I'll probably change SetParameter into two overloads - one with (value) parameter and other with (name, value) pair.<BR/><BR/>- As of the message passing - see the next example (most probably published today).gabr42https://www.blogger.com/profile/06903558857617342477noreply@blogger.comtag:blogger.com,1999:blog-29331675.post-32043683105781354782008-07-03T10:44:00.000+02:002008-07-03T10:44:00.000+02:00Hi,I am looking forward to the next installment. W...Hi,<BR/><BR/>I am looking forward to the next installment. What I have seen so far looks like you have quite a lot experience with multithreaded applications. Since I am currently maintaining / extending a multithreaded app as well, I am seriously thinking about using your library. Inter thread communication is usually the biggest challenge.<BR/><BR/>twmAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-29331675.post-21459820288180178122008-07-03T06:50:00.000+02:002008-07-03T06:50:00.000+02:00Intersting idea worth of a little looking. Passin...Intersting idea worth of a little looking. Passing info into the thread seems a little klunky tho.<BR/><BR/>It isn't <BR/><BR/>12 := a, or let 12 =a, or even usually mov 12,ax, so I think you have the parameter name/value concept reverse to both natural patterns and common patterns of usage.<BR/><BR/>Message passing after the fact also looks it it needs more encapsulating to lower the coding overhead.<BR/><BR/>But aside from that, like I say, definitely interesting.Anonymousnoreply@blogger.com