This is not what I want to read after just purchasing it !! Are you talking about the Win32 side of things, or the .Net....or the whole lot?
Jeremy -----Original Message----- From: Kyley Harris <[EMAIL PROTECTED]> To: NZ Borland Developers Group - Delphi List <[email protected]> Date: Tue, 19 Jul 2005 14:28:54 +1200 Subject: [DUG] Stopped Using D2005 > well, after months of trying and frustrating patience, I have left > delphi 2005 and gone back to developing with Delphi 7. > > 1. I can almost never debug a threaded application. The entire computer > goes into a locked up state where no mouse or keystrokes are processed > by the computer (I have heard * read of others with the same problem) > > 2. The compiler doesn't always compile properly. yesterday, I removed a > unit from a uses clause, and build all still worked, even though i had > plenty of references to the unit. It kept working until I restarted > delphi. Finally got the error messages. > > 3. The memory leaks are beyond useful. Crashes all the time. Even tried > the FastMM patch of the Borlandmm.dll to fix the memory leaks and > stuff. > unfortunately all the workarounds came to the fore and it was no > better. > > 4..1000 (More of the above) I wonder what the chances of a refund are? > Out of the box, for doing what Delphi 7 did reasonably ok, this has > failed and failed. Perhaps when using the C# or the .Net it works > better, i don't know. > > ANYONE who does not know about QC14007 in quality central should read > it. That one bug alone is the reason why we should all get an Update 4, > or a refund. not D2006 (unless it is update 4). > > regards > Kyley > > > _______________________________________________ > Delphi mailing list > [email protected] > http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi
