"Fyi", this might be useful, or it might not be, or it might seem useful and
then not be.
I tried out "Services for Unix" recently.
I noticed in taskmgr stuff without ".exe" extensions.
This got me experimenting.
Leading to these findings:
CreateProcess does not care about extension. Or at least, it can run
extensionless executables. I can't vouch for batch files and 16 bit files.
The usual Windows command line, cmd, does care.It does some sort of nested
search over %PATH% and %PATHEXT%.PATHEXT is a list of extensions that are
runnable.
If youset PATHEXT=.;%PATHEXT%
then cmd as well can run extensionless executables.
If you are living in "your own" sh/ksh/bash/xterm/rxvt that youcan
control/change/"fix", then you can "just do this" -- createextensionless files.
If you don't mind cmd users having to alter PATHEXT, ditto.
But if you want interop with a default cmd environment, then this is useless
trivia.
I didn't experiment with running stuff from the Explorer GUI.i.e. if you are
creating Windows GUI apps...don't know.Maybe you can make an "association" (see
the ftype and assoccommands).
Similarly but less intesting, .dlls can have any extension..so works.Python
extensions use like .pyd for Python dll I guess.
This is much less interesting because .dll extensions already vary across Unix
systems and are already never (?) extensionless.
I created and used a bunch of extensionless executables for a fewdays and the
experience was "ok" but I decided not worth buckingthe trend -- this was with
work involving Cygwin.
- Jay
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users
