Compiler manual says:
I have worked with this limitation for many years, and my complex code looked ugly where I had to comply to this rule and avoid code indentation. However, in code example below {$X-} switch works even when intended in code:
Does this mean that compiler finally doesn't care if we intend compiler switches to beautify our code? If so then manual should be updated.
:3some:
btw. I am aware of {$DEBDELAY} and "Short mDelay" menu switch in simulator, but there is code with many delays where my mDelaySim() is essential for simulation.
Zitat
The switches must start in the first column of a line.
I have worked with this limitation for many years, and my complex code looked ugly where I had to comply to this rule and avoid code indentation. However, in code example below {$X-} switch works even when intended in code:
Code
{ $D-} // do not step following code in debuger
procedure mDelaySim(const msec: word);
begin
{$X-} // do not execute following code in simulator
mDelay(msec);
{$X+}
end;
{ $D+}
procedure mDelaySim(const msec: word);
begin
{$X-} // do not execute following code in simulator
mDelay(msec);
{$X+}
end;
{ $D+}
Does this mean that compiler finally doesn't care if we intend compiler switches to beautify our code? If so then manual should be updated.
:3some:
btw. I am aware of {$DEBDELAY} and "Short mDelay" menu switch in simulator, but there is code with many delays where my mDelaySim() is essential for simulation.
