views:

1528

answers:

4

Is there a Delphi equivalent of the C# #if(DEBUG) compiler directive?

+9  A: 

Use this:

{$IFDEF DEBUG}
...
{$ENDIF}
Lasse V. Karlsen
And make sure the project options define DEBUG. I think only the newer Delphi (D2007 and up?) versions set it by default for a debug build.
Lars Truijens
For older versions you can use {$IFOPT D+}. 'D' is the compiler option symbol for "Compile with Debug Info". 'D+' indicates that what follows should only be compiled if that option is *ON*.
Deltics
For portability of the more readable {$IFDEF DEBUG} you could of course include something like {$IFOPT C+}{$DEFINE DEBUG}{$ENDIF} in a standard defines include file (in the sections relating to versions of Delphi that don't auto-define DEBUG for you. Note however that this "auto-define" is not always reliable. DEBUGINFO I think is auto-defined but DEBUG is only defined if you leave the default conditionals for the DEBUG build as they are (they include DEBUG as a "factory" setting, but this can and may be removed. i.e. It's not a "built-in" definition when building with Debug Info on.
Deltics
+4  A: 

Apart from what lassevk said, you can also use a few other methods of compiler-evaluation (since Delphi 6, I believe) :

{$IF NOT DEFINED(SOME_SYMBOL)} 
  // Mind you : The NOT above is optional
{$ELSE}
{IFEND}

To check if the compiler has this feature, use :

 {$IFDEF CONDITIONALEXPRESSIONS}

There are several uses for this.

For example, you could check the version of the RTL; From the Delphi help :

You can use RTLVersion in $IF expressions to test the runtime library version level independently of the compiler version level.
Example: {$IF RTLVersion >= 16.2} ... {$IFEND}

Also, the compiler version itself can be checked, again from the code:

CompilerVersion is assigned a value by the compiler when the system unit is compiled. It indicates the revision level of the compiler features / language syntax, which may advance independently of the RTLVersion. CompilerVersion can be tested in $IF expressions and should be used instead of testing for the VERxxx conditional define. Always test for greater than or less than a known revision level. It's a bad idea to test for a specific revision level.

Another thing I do regularly, is define a symbol when it's not defined yet (nice for forward-compatiblity), like this :

 {$IF NOT DEFINED(UTF8String)}
 type
   UTF8String = type AnsiString;
 {$IFEND}

Hope this helps!

PatrickvL
+1  A: 

These control directives are available:

{$IFDEF}
{$ELSE}
{$ENDIF}
{$IFNDEF} //if *not* defined

and they can be used as shown here:

procedure TfrmMain.Button1Click(Sender: TObject);
begin
  {$IFDEF MY_CONDITIONAL}
  ShowMessage('my conditional IS defined!');
  {$ELSE}
  ShowMessage('my conditional is NOT defined!');
  {$ENDIF}

  {$IFNDEF MY_CONDITIONAL}
  ShowMessage('My conditional is explicitly NOT defined');
  {$ENDIF}
end;
JosephStyons
You forgot {$IFOPT}, which can be used to directly test for compiler settings.{$IFOPT D+} // DEBUG INFO ON{$IFOPT C+} // ASSERTIONS ENABLEDetc
Deltics
+2  A: 

DebugHook is set if an application is running under the IDE debugger. Not the same as a compiler directive but still pretty useful. For example:

ReportMemoryLeaksOnShutdown := DebugHook <> 0; // show memory leaks when debugging
Lawrence Barsanti