|
SDTimes故事：C++ Builder X: 复仇出击 (English)(2)
In fact, the IDE, LeBlanc said, “adopted an IDE framework, internal to Borland, which is also used by JBuilder.” That 5-year-old Java-based IDE gives C++ Builder X some of its new features, such as pluggable compilers, project files stored in XML documents, and compatibility with Borland’s other tools, such as Teamstudio collaboration software, CaliberRM requirements manager and the Together modeler.
Because the Java IDE code is portable, said LeBlanc, for the first time C++ Builder runs on Solaris, as well as Linux and Windows out of the box. “We never had a tool chain for C++ that ran on an enterprise platform such as Solaris,” he said.
Another benefit: C++ Builder X is now compiler tool-chain agnostic, according to LeBlanc. Some editions of the new C++ environment, which shipped in mid-September, include Borland’s C++ compiler for Windows; Microsoft’s Visual C++ compiler; GCC for Linux, Solaris and Windows; and Intel’s C++ 7.1 compilers for Linux and Windows. Not in the box, but supported if the developer owns it, are the Metrowerks C++ compiler and Sun’s Forte C++ compiler for Solaris on SPARC processors.
According to LeBlanc, developers can plug other compilers in as well. “If you have a special compiler, as is common in the embedded space, you can easily plug it in.
“There’s no one compiler that’s best,” he continued. “If you’re looking for performance on the runtime, that’s one compiler; if you’re looking for performance at compile time, you might choose another.”
Indeed, admitted LeBlanc, “since our focus has been on rapid application development, we tend to focus on compile time; we’d be good, but not great, at runtime. Whereas you have the Intel compilers that are Excellent at runtime—they’re the fastest—but at compile time, they could be slow.”
|
