On 2020-11-27 15:34, Bart via fpc-devel wrote:
On Thu, Nov 26, 2020 at 11:10 PM Tomas Hajny via fpc-devel
<fpc-devel@lists.freepascal.org> wrote:
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.
Well, at my machine it did not.
I also called it from a batchfile (as break.exe) to see if I could
catch the errorlevel (I let it crash with a division by zero).
The errorlevel is set, but absolutely no output to screen or pipe.
Understood. Haven't I already mentioned something about MS approach
towards compatibility here recently? :/
-------------------
D:\TEMP>cmd
Microsoft Windows [Version 10.0.18363.1082]
(c) 2019 Microsoft Corporation. Všechna práva vyhrazena.
D:\TEMP>break
D:\TEMP>break.exe
I am Break
D:\TEMP>.\break
I am Break
D:\TEMP>
===================
Tomas
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
