Jump to content

EddieDee

Members
 View Profile  See their activity

  • Content Count

    3

  • Joined

  • Last visited

Posts posted by EddieDee

  1. Posted

    4 hours ago, Remy Lebeau said:

    Honestly, I have yet to try any of the Clang compilers at all, and while I would love to be able to use newer C++ language features in my code, this issue just reaffirms why I have no desire to EVER use the Clang compilers.  They are just not supported properly in the IDE or the libraries.  Too many problems that are "solved" by using the classic compiler instead.

    That's what I'm quickly finding out! All that the Clang compilers have done is forced me to modify code that really never needed modifying! I never realized there was a way to switch it back to the "classic" world until yesterday.

     

    But it's still light years better than using Visual Studio! :-)

  2. Posted

    While digging further into this today, I discovered that if I switched the compiler to the 'classic' bcc32 compiler the debugger issue went away and I was able to see the evaluation of the variable without any issues. So it seems that this is a "feature" of the non-classic compiler.

    Quote

    Why are you concatenating a WIDE string literal to an ANSI string?  You should drop the 'L' prefix, it doesn't really belong there.

    True. And I did try it both with and without a wide literal string. I got the same results both ways.

  3. Posted

    I've been using C++ Builder since v1, and until Windows 7 broke my copy of C++ Builder 3 I used it regularly.

     

    So I recently discovered Embarcadero has the community edition of C++ Builder, and so I downloaded it. Unfortunately it is a convoluted mess to me, as I HATE using unicode strings! Give me the old days! :-)

     

    But I've managed to convert most of my code over now, but ran into an odd problem. I have a few lines of code that don't seem to be working. Here's an example:

      

    AnsiString s;
s = Form1->InputString;
s += L" - Some Extra Text.";

    When I set a breakpoint on the next line of code, then examine s, I see: 

    > s { ???? }

    instead of what should be there! In this case, InputString is an AnsiString that contains the text "Start Here". If I examine that variable I see:

      

    > InputString { "Start Here" }

    So, shouldn't I see: 

    > InputString { "Start Here - Some Extra Text" }

    when I examine s?

     

    This makes no sense to me! Especially when I move the breakpoint to the concatenation line and examine s before the "Extra Text" is added. As it still shows { ???? } when I evaluate it!

     

    Any ideas?

×