Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/nodejs/node.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBert Belder <bertbelder@gmail.com>2010-11-26 20:40:23 +0300
committerBert Belder <bertbelder@gmail.com>2010-12-21 01:51:23 +0300
commit6d266219cc8603ea7034685e6f5afffae2a6ff2f (patch)
tree00e8299674a645702979470043535fef4c559d05 /TODO.win32
parente047ec340dc2bfa0cc0dec40a19b14f36462c7ee (diff)
Add more stuff to TODO.win32
Diffstat (limited to 'TODO.win32')
-rw-r--r--TODO.win3212
1 files changed, 10 insertions, 2 deletions
diff --git a/TODO.win32 b/TODO.win32
index 3f80152250e..35acaeb64a5 100644
--- a/TODO.win32
+++ b/TODO.win32
@@ -1,13 +1,17 @@
- Implement setenv / unsetenv
- Implement other stuff missing in node.cc/process
- Like setuid, setgid, kill etc.
+ Like getuid, getgid, setgid, kill etc.
- Implement missing `net` methods
A pressing issue is: how do we work with windows api functions that are not utf8 aware?
E.g. getaddrinfo() is ansi-only; GetAddrInfoW is utf16-only. Can we get utf16 straight out of v8?
+ Are unix sockets similar to windows named pipes? If so, should they be supported? -> currently: no. Complication: they block.
- Child processes
+ Should not be too hard using CreatePipe, CreateProcessW and GetExitCodeProcess.
+ When customFds are specified, should we support hooking up to a socket fd?
+ How can we distinguish between the exit code and exception number after calling GetExitCodeProcess?
- Stdio (make TTY's / repl / readline work)
This will be hard: there is no ANSI escape code support in windows.
@@ -32,7 +36,7 @@
If _open_osfhandle fails but socket doesn't, a stray handle is left open. It should be fixed.
- Check error number mappings.
- Winsock errnos are different.
+ Winsock errnos are sometimes different.
- Think about `make install`
@@ -41,6 +45,10 @@
- Link pthreads-w32 statically by default
+- Link Mingw libraries statically by default
+ Like libstdc++.dll, more maybe.
+ Microsoft libs are always there, no static linkage required (e.g. msvcrt, winsock2).
+
- Make (open?)SSL work
- Support using shared libs (libeio, v8, c-ares)