If you want to use c + + 11, can only use a 64 - bit compiled, if original 32-bit, cannot use, unexpectedly, cbuilder even compiler now, no unified, 32-bit compiler or old, new, with a clang
CodePudding user response:
Seems to support the 10.3, c + + 17,
CodePudding user response:
32-bit compiler choose clang 11 or Borland c + + compiler options here:
C + + Compiler - & gt; The Classic Compiler - & gt; The Use of 'classic' Borland compiler, 32 - bit Windows platform only:
If you choose the true, the use of past Borland compiler, this is the default option of 32-bit compiler
If you choose the false, use the new clang compiler, support for c + + 11
CodePudding user response:
refer to the second floor ybchen response: 32-bit compiler choose clang 11 or Borland c + + compiler options here: C + + Compiler - & gt; The Classic Compiler - & gt; The Use of 'classic' Borland compiler, 32 - bit Windows platform only: If you choose the true, the use of past Borland compiler, this is the default option of 32-bit compiler If you choose the false, use the new clang compiler, support for c + + 11 CodePudding user response:
Choose CLang, Calder uh-uh, can stuck in edit mode CodePudding user response:
Old cat is silly cat... CodePudding user response:
reference 4 floor vc_dreamver response: choose CLang, Calder uh-uh, in edit mode can be jammed c + + Builder now no cattle people, these compilers, all make uncertain, CodePudding user response:
refer to 6th floor zdhsoft response: Quote: refer to 4th floor vc_dreamver response: Choose CLang, Calder uh-uh, in edit mode can be jammed c + + Builder now no cattle people, these compilers, all make uncertain, Clang/LLVM claiming compilation speed is three times the GCC... CodePudding user response:
CodePudding user response:
refer to 7th floor DelphiGuy response: Quote: refer to the sixth floor zdhsoft response: Quote: refer to 4th floor vc_dreamver response: Choose CLang, Calder uh-uh, in edit mode can be jammed c + + Builder now no cattle people, these compilers, all make uncertain, Clang/LLVM claiming compilation speed is three times the GCC... Clang is soon... Used, but the BCB in it, not necessarily, CodePudding user response:
refer to the eighth floor ccrun response: CodePudding user response:
references 9 f zdhsoft response: Quote: refer to 7th floor DelphiGuy response: Quote: refer to the sixth floor zdhsoft response: Quote: refer to 4th floor vc_dreamver response: Choose CLang, Calder uh-uh, in edit mode can be jammed c + + Builder now no cattle people, these compilers, all make uncertain, Clang/LLVM claiming compilation speed is three times the GCC... Clang is soon... Used, but the BCB in it, not necessarily. Can only say that of real-time syntax check this task is not fast enough... CodePudding user response:
11 references DelphiGuy response: Quote: references 9 f zdhsoft response: Quote: refer to 7th floor DelphiGuy response: Quote: refer to the sixth floor zdhsoft response: Quote: refer to 4th floor vc_dreamver response: Choose CLang, Calder uh-uh, in edit mode can be jammed c + + Builder now no cattle people, these compilers, all make uncertain, Clang/LLVM claiming compilation speed is three times the GCC... Clang is soon... Used, but the BCB in it, not necessarily. Can only say that of real-time syntax check this task is not fast enough... C + + Builder, mainly is no cow, so ha ha ha CodePudding user response:
reference 13 floor zdhsoft reply: Quote: reference 11 floor DelphiGuy response: Quote: references 9 floor zdhsoft response: Quote: refer to 7th floor DelphiGuy response: Quote: refer to the sixth floor zdhsoft response: Quote: refer to 4th floor vc_dreamver response: Choose CLang, Calder uh-uh, in edit mode can be jammed c + + Builder now no cattle people, these compilers, all make uncertain, Clang/LLVM claiming compilation speed is three times the GCC... Clang is soon... Used, but the BCB in it, not necessarily. Can only say that of real-time syntax check this task is not fast enough... C + + Builder, mainly is no cow, so ha ha ha nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull