On 2020-11-26 20:17, Bart via fpc-devel wrote:
On Thu, Nov 26, 2020 at 6:52 PM Jonas Maebe via fpc-devel
<fpc-devel@lists.freepascal.org> wrote:
"break" is probably a command that's recognised by the cmd shell.
Yes it is:
C:\Users\Bart>help break
Sets or Clears Extended CTRL+C checking on DOS system
This is present for Compatibility with DOS systems. It has no effect
under Windows.
If Command Extensions are enabled, and running on the Windows
platform, then the BREAK command will enter a hard coded breakpoint
if being debugged by a debugger.
Try to
execute the program as .\break or break.exe
Makes no difference whatsoever.
It does run, because you can set ExitCode and query errorlevel after
execution.
Typing 'break.exe' in cmd.exe _does_ make a difference here (it executes
as expected unlike when typing just 'break'). And obviously running
break.exe using some other 'shell' (e.g. your preferred OFM ;-) ) works
as well.
Tomas
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
