views:

97

answers:

1

I have the construct:

{$ifopt FINITEFLOAT ON}
  {$message 'FINITEFLOAT option ON' }
{$else }
  {$message 'FINITEFLOAT option OFF' }
{$endif }

in my source and it won't compile! It's got to be something stupid. The error is:

E1030 Invalid compiler directive: '$IFOPT'

at the first line, but it is the FINITEFLOAT it's complaining about. You don't seem to be able to specify anything except the single letter directives like R+ etc as the argument of IFOPT.

Am I missing something here?

+4  A: 

You are totally correct AFAICT. I don't use $IFOPT often but everytime I do this behaviour annoys me. I have no idea why this is implemented this way.

Edit: There's a Quality Central issue for this.

Ulrich Gerhardt
Just found this: "http://docwiki.embarcadero.com/RADStudio/en/X1030_Invalid_compiler_directive_-_'%25s'_(Delphi)" (quoted URL as S/O doesn't parse the URL properly if it ends in a ")"). And I see the QC. Unbelievable. So I can't report the state of a compiler option that doesn't have an abbreviated form?
Aside. Found my posting in a google search less than 15 minutes after submitting it. Now that's quick.