BCB6.0 is 20 reasons for garbage

zhaozj2021-02-16  46

The BCB6.0 and Windows2000 I use are all genuine company, and I have experience in development.

1. The IDE often occurs illegally, and sometimes the restart will be wrong, and it is necessary to reload the BCB.

2. Automatic completion and smart prompts are slower, slow to get a cup of coffee.

3. The above two functions often lead to an error message, and the optimal phase information frame is not moving.

4. VCL Curre bug countless, just write a program, with a self-contained memory check tool, there is memory leak.

5. When compiling the link, Mingming is often wrong, and then makes it a good time, sometimes it needs to be edited.

6. No matter how to change the compilation option, you cannot set a breakpoint in debugging.

7. Compile, the link speed is slower, which is unbearable.

8. C class library is actually Pascal source code.

9. Cancer when walking, or an error.

10. The editor is too small, there is no macro, nor does it customly a custom keyboard.

11. Ide itself not only accounts for huge memory, but also memory leaks, insufficient memory after long use.

12. Multiple engineering does not detect which project needs to be recompiled, resulting in running confusion.

13. Even a small change, it is also necessary to compile the entire project, and the incremental compilation is huge, which is true.

14. There is no incremental link function.

15. There is no editor's continuation function.

16. The WINDOWS program-compiled Windows program is extremely low, and the file size is huge.

17. The memory when debugging is very difficult to use.

18. For the management of big projects, the larger the project, the more problems.

19. Starting and exiting is super slow, often unable to respond.

20. The included tool is more than one time, you will know that the tools and SPY similar tools will know.

转载请注明原文地址:https://www.9cbs.com/read-19827.html

New Post(0)