Vitaliy wrote:
>> Interesting!  I've had it running 24/7 for months with no problem.
> 
> On what sort of hardware? AsyncPro problems started appearing after 
> multi-core systems became commonplace.

Yup - the one I ran it on most is pre-hyperthreading.  The other one 
it's run on a bit has hyperthreading turned off.  (Caused lots of 
problems and also slowed down whatever I was doing at the time...)

> Yeah, installed it a couple of days ago, just haven't had a chance to try 
> it. I was a little bit put off by the naming convention, and the comments 
> written in broken English. So I made a last ditch attempt to try to find a 
> fix for AsyncP. :)

!

>> Yes, it's a very good spot for a facade.  You never know when you'll
>> need to make the same app work over TCP/IP or whatever.
> 
> My reasoning was that I've already switched libraries once, and may need to 
> switch again. Are you into patterns?

In general, yes - I think it was a much-needed step, and the Gamma set 
is a very useful vocabulary.

> On the other hand, the software architect is the same. :) Based on my brief 
> encounter with C# two years ago, both the language and the IDE are not that 
> much different from Delphi.

Yes.  I still lose sleep over him going over to the Dark Side so they'll 
have something to tempt us with.

(not really)

(but it is annoying)

> Do you think [Delphi] will be around much longer? One argument I keep hearing, is 
> that it's easier to find/hire C# programmers, and that Delphi programmers 
> are jumping ship.

It was argued that C++ was going to kill Delphi, then Java was, now C#. 
  Which doesn't mean Delphi is thriving.  But it sure has lasted a long 
time.

Right now the main thing Delphi lacks for me is platform-portability, 
and Python/wxWindows seems more portable than .NET, so I've been moving 
in that direction.
-- 
Timothy J. Weber
http://timothyweber.org
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist