And if it should require the "use Cygwin;" importer. Probably so. The current list of 6 cygwin functions in core require no "use Cygwin;".
I came up with this list for a future Cygwin package:
cygserver_running() => bool
CW_GETVERSIONINFO() => str
CW_GET_CYGDRIVE_PREFIXES($user, $system) => flags as str
CW_SET_CYGWIN_REGISTRY_NAME($path)
CW_GET_CYGWIN_REGISTRY_NAME => str
CW_STRACE_ACTIVE() => bool
CW_EXTRACT_DOMAIN_AND_USER(\%pw) => (domain, user)
CW_CMDLINE($pid) => str
CW_CHECK_NTSEC($filename) => bool
CW_GET_ERRNO_FROM_WINERROR($error, $deferrno) => int
CW_GET_POSIX_SECURITY_ATTRIBUTE($attribute, \@psa) => \%sd
CW_GET_SHMLBA() => GetSystemInfo.dwAllocationGranularity
CW_GET_UID_FROM_SID($psid) => $uid
CW_GET_GID_FROM_SID($psid) => $gid
Of course CW_ will be removed and properly lower cased. Look up sys/cygwin.h and/or winsup/external.cc for example.
Future Cygwin:: enhancements 0 Comments More | Login | Reply /