Re:BDS 2006 - VERY disappointed ...
Hi Nick,
Quote
I have been enountering numerous errors, unable to compile,
I had a bad OMF record in the VCL.bpi,
I don't know what's up here, I hope David or Remy can help... (guys?)
Quote
the "Find in Files" can NOT find anything beyond the current opened file - what the hell!
I use this every day and had no problem, I do have a wild guess though...
I have also move some major apps from BCB6 to BDS2006. These guys STRONGLY
recommended that I NOT use the translation mode, but instead start a NEW
project and ADD the files to it (I know my way around the make (bpr) files
but I couldn't quite get it ALL figured out). Point is this will eliminate
many problems. And it's not as much of a unmitigated tedious pain in the...
as it sounds...
Quote
This is not the type of thing I have come to expect from a world class leader, especially at about $5k Cdn.
My immediate concern is with the de{*word*81}.
Did you know the de{*word*81} will step through code, but skip over lines with code and step onto blank lines.
I thought Borland had resolved this.
BEcause of this, I have NOT been able to migrate my BCB6Ent project to BDS.
Does ANYONE have any idea why the de{*word*81} is doing this, and how can I resolve it?
This is part of my reply to the message 'Debug tracing off' by William Riley above.
(it's somewhat out of context..)
As I think you may have guessed the failure of the
code displayed to synchronize with the recompiled code
when not doing a complete (re)Build is very common.
I have also seen this when the compiler 'optimizes'
code. This occurs in some form whether 'Optimizations'
are turned on or not.
For example where you have code that processes data that
is never accessed (if you have not written that section
yet for example). Sometimes the de{*word*81} gets out of sync.
Being as there is no underlying assembly code to sync too.
I hope that helps. The products not perfect but it does actually work.
Bruce Larrabee
{smallsort}
