Home/ Questions/Q 146075
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T08:32:13+00:00

I work in Delphi 2007 (both win32 and .Net) but the CodeGear IDE frequently

  • 0

I work in Delphi 2007 (both win32 and .Net) but the CodeGear IDE frequently annoys me, so if possible I’d like to find a replacemnt.

We have a build script so I can compile from the command line and I very rarely do any GUI designing, so the only thing I need is a text editor (with syntax highlighting, Autocomplete/Intellisense …).

I would like to use Visual Studio or Emacs but don’t know how feasible it is to work on Delphi code in those environments. Particularly debugging – can the Delphi IDE still act as my debugger even if I don’t use it for editing?

Does anyone have any experience of breaking away from RAD studio?

P.S. I am aware of the new Delphi Prism but that won’t solve my problems – I still need to work in vanilla Delphi and use the Delphi 2007 compiler.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. You can of course edit source files outside of the Delphi IDE. When you switch back to the IDE it will notice that files have been changed outside of it, and ask you whether to reload them (if they are currently opened in the editor). This is a safe thing to do if you never edit inside the IDE, but to keep the confirmations from appearing it is best to not have source files open in the Delphi editor at all while you edit them in emacs.

    Even if you use a custom build script and build the project from emacs you should still keep the project file up-to-date. When you use the debugger in the IDE it will usually first compile the project. To have this always work (even with visual form or frame inheritance) a correct project file is crucial. It is also important for debugging when you have several source files with the same name in different directories that are in your search / browse path, or if you have not all your source directories in the search / browse path.

    Whatever tools you use for editing or otherwise changing your source files, make sure that you always have DOS style CR+LF line endings (\r\n, #13#10) in all lines, as LF only (\n, #10) tends to confuse the IDE – you will notice that the blue dots in the debugger are out of sync with the source lines, and that compiler error line numbers are wrong. Using sed or awk on source files can be a big time saver, but be sure to use the tools compiled for Win32, and not those provided with (for example) the cygwin environment.

    • 0