Anoop Thomas Mathew wrote: > What's your opinion about a project in VIMas an on the fly code checker.
I really think you should consider composing a new email thread instead of piggy backing on another email thread; especially one that has nothing to do with your topic and already is full of entries. Translated: you're missing your target audience. > > Steps > --------- > i.That is VIM text to a temporary file. > ii.Compile it with a compiler.(Either use an external compiler ( > preferred by Mr. Moolenaar) or to write an independent parser plug-in > within VIM) > iii.Then re-parse the error messages. > > This is my proposed idea for Google Summer of Code 2008. > Is there any mistake or faults.Please guide me out. If you want speed, you need to do the syntax checking yourself, which probably means a LALR parser (ie. an equivalent of yacc). If speed is of little concern, your approach might work, although o/s's that lack decent multi-tasking would make the use of this unpleasant. When I start coding, I often use a template, so I start off with a valid C/C++ program. However, there are plenty of times that the code is in-development, and not ready for compiling. I think I'd find this annoying, but I'm willing to be pleasantly surprised. I have vim-commands that compile and check code; the checking (called :Chk for some reason!) uses Vim's quickfix so I can relatively cleanly handle compiler errors/warnings without leaving the editor. However, there are projects that I work with that :Chk doesn't work correctly for (largely due to the need for compiler options, special libraries, etc, and the knowledge to compile correctly is embedded in a Makefile). Thus you undoubtedly will have some gotchas in coding this that you're not currently aware of. Regards, Chip Campbell --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
