Mike Williams wrote:
> >> Attached is a patch against 7.1.082 to solve a number of issues with > >> cscope on Windows. It no longer jumps through hoops to hide the console > >> (occasionally failing), fixes a handle leak when killing a connection, > >> now reports a process id, and simplifies the Win32 code logic creating > >> the connection. One consequence of the change is that VIM now has to > >> explicitly exit the processes running cscope. Windows has no concept of > >> patent child processes like Unix - I assume _spawnl() used previously > >> tracked child process ids and used an atexit() style method to clear > >> them up. > >> > >> I can't currently test Unix builds so I don't know if I have broken > >> them. I haven't tested with BorlandC - from the documentation I have > >> seen it is all bog standard Win32 API, and should all work from Win98 > >> onwards. Problem reports more than welcome. > > > > Thanks for working on this problem and making this patch. > > > > I'll put it in my todo list, and await remarks in the mean time. > > Ok, I have tested it on OpenBSD 4.1 and it still compiles and runs, so I > guess that passes the Unix test. Which is nice. Good. > However, in passing, the default vim build on OBSD throws a warning > during the autoconf process (wrapped, sorry): > > configure: WARNING: sys/sysctl.h: present but cannot be compiled > configure: WARNING: sys/sysctl.h: check for missing prerequisite > headers? > configure: WARNING: sys/sysctl.h: see the Autoconf documentation > configure: WARNING: sys/sysctl.h: section "Present But Cannot Be > Compiled" > configure: WARNING: sys/sysctl.h: proceeding with the preprocessor's result > configure: WARNING: sys/sysctl.h: in the future, the compiler will take > precedence > configure: WARNING: ## ------------------------------------------ ## > configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. ## > configure: WARNING: ## ------------------------------------------ ## > > Checking the ports tree it looks like the OBSD maintainer has a patch > for this - is there any particular reason why it can't be rolled into > the main sources? The reason is that I don't have the patch. It might be that the problem is OpenBSD specific (an error in sys/sysctl.h probably). It's a pity that a tool that was made to help make programs portable isn't portable... -- hundred-and-one symptoms of being an internet addict: 233. You start dreaming about web pages...in html. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
