StarWing wrote: >> How about some documentation? So that we know how it's supposed to >> work. >> >> -- >> hundred-and-one symptoms of being an internet addict: >> 134. You consider bandwidth to be more important than carats. >> > > documentation is on the way... i find it's hard to write, because some > features are not stable, next version of the patch file will includes > the documents. > > one word, it's a interface for process interaction with writting some > simple Vim scriopt. it will be more flexible than implement vimshell & > vimgdb with patch file. > Hello, StarWing:
I'd like it if cross-platform dlopen/LoadLibrary was working better. I use vim's libcall which maps to (linux: libcall) (windows: LoadLibrary) but every time libcall() is used the library gets re-opened. Never seems to be closed, either. One effect: one can't have static variables in the external library (which is what precludes many system calls). My gdbmgr (http://mysite.verizon.net/astronaut/vim/index.html#GDBMGR) uses libcall() anyway; I work around the static variable limitation by using shared memory. If you're interested, you can see some snapshots: http://mysite.verizon.net/astronaut/pix/gdbmgr1.jpg http://mysite.verizon.net/astronaut/pix/gdbmgr2.jpg Regards, Chip Campbell --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
