Changing soffice.bin to be console application on Windows

[Stephan Bergmann]

On 19/11/2018 16:38, Kaganski Mike wrote:
> I have prepared a patch making soffice.bin a proper console Windows
> application: https://gerrit.libreoffice.org/63572. The patch also
> introduces a new launcher soffice.com (in addition to existing
> soffice.exe). That is to make possible to call soffice from command
> line, and have proper console launcher for that call.

If there's both soffice.exe and soffice.com in the same directory 
(assuming the "new launcher osffice.com" also goes into program\), what 
will happen if some client starts just soffice w/o extension (either 
from a shell, or from Windows' equivalent of exec, if it's possible to 
call that w/o an extension)?  (program\soffice.exe is part of the stable 
3rd-party interface on Windows, but I'm not sure whether we officially 
announce it as "program\soffice.exe is part of the stable interface" (so 
client code could be considered broken if it calls that w/o extension) 
or as "program\soffice is part of the stable interface".)