THE END (of Borland C++ Builder)?

I've been looking to upgrade my compiler from my trusty BCB5, but have been worried (and confused) by what I've been reading...

:confused:

Found this Open Letter from Borland...

http://bdn.borland.com/article/0,1410,31277,00.html

Is it the case that Borland are ceasing to support C++ Builder, or more specifically are they planning to cease support for C++ with CLX?

I note in their open letter, they recommend Windows C++ developers switch to using their stuff for .NET. If this is the case, it looks to me like it would be better to switch to Microsoft (sorry Borland).

Also, anyone know what Borland's wxWindows stuff is? Is it an equivalent of CLX, or a different beast entirely?

Quote:

---

they recommend Windows C++ developers switch to using their stuff for .NET. If this is the case, it looks to me like it would be better to switch to Microsoft (sorry Borland).

---

IMHO Microsoft's Visual Studio IDE would probably be better if you're targeting .NET. Their Delphi product is also migrating to .NET.

Quote:

---

Also, anyone know what Borland's wxWindows stuff is? Is it an equivalent of CLX, or a different beast entirely?

---

They're using the open source wxWidgets (formally called wxWindows).. The API is pretty simple, but the .exes generated are painfully large (compared to plain Win32 API). But the development time you save will probably outweight some of the disadvantages.

Well, I don't want to particularly target .NET, but I do want to target Windows. What I loved about the VCL/CLX is that it provided a really efficient wrapper around the Win API. It is this I really want.

I'm a bit annoyed with Borland cos with BCB6 (which I've been trialing) they're urging people to port all their VCL code to CLX, which now is looking like a completely pointless exercise.

The wxWindows stuff looks like it maybe worth looking into.

Guess I'll have to do some thinking & research.