Re: GSOC: On-the-fly Code Checking for Vim - Challenges

Congradulations, Birgi! Don't know whether you have looked into anything about Eclipse, but I referred to their documentation and learned a lot there. They also talked about how incremental compiling works:

Re: GSOC: On-the-fly Code Checking for Vim - Challenges

On Apr 21, 10:09 pm, Lin [EMAIL PROTECTED] wrote: Congradulations, Birgi! Thank you very much Lin :), I am very happy to be involved. Don't know whether you have looked into anything about Eclipse, but I referred to their documentation and learned a lot there. They also talked about how

Re: GSOC: On-the-fly Code Checking for Vim - Challenges

Lin wrote: Hi all, [...] To let the syntax checker see the buffer, I think the solution can only be making copies of related files The Flymake plug-in for Emacs, as already referred to in the first post, seems to be running some reasonable heuristics on finding the related files. But

Re: GSOC: On-the-fly Code Checking for Vim - Challenges

Hello everyone, This is another student who is applying for the on-the-fly code checker project in GSoC. On Apr 14, 2:59 am, [EMAIL PROTECTED] wrote: However, I do am interested in something able to understand C++ constructs in order to built even more powerful code transformations and

Re: GSOC: On-the-fly Code Checking for Vim - Challenges

Bram Moolenaar wrote: Birgi Tamersoy wrote: Hey everybody, Apparently many students (like me) are interested in this project. So, I decided to start a new thread where we can talk about the challenges in the project and how to solve them. I went over previous posts to include all the

Re: GSOC: On-the-fly Code Checking for Vim - Challenges

Lin [EMAIL PROTECTED] wrote: This is another student who is applying for the on-the-fly code checker project in GSoC. On Apr 14, 2:59 am, [EMAIL PROTECTED] wrote: However, I do am interested in something able to understand C++ constructs in order to built even more powerful code

Re: GSOC: On-the-fly Code Checking for Vim - Challenges

There are yacc grammars available for several languages, including C, Matlab, and Lisp. The advantage of this approach is similar to the advantage of the syntax highlighting engine; its not particularly tied to any language. I mostly program in C/Matlab myself, but I know there's plenty of

Re: GSOC: On-the-fly Code Checking for Vim - Challenges

On Apr 14, 11:18 pm, Charles E Campbell Jr [EMAIL PROTECTED] wrote: The primary disadvantage is that effectively writing a new yacc/bison is not a small task. I have a real thick book about writing a yacc-like parser somewhere; if anyone's interested, I could look up its ISBN. The biggest

Re: GSOC: On-the-fly Code Checking for Vim - Challenges

On Monday 14 April 2008, Lin wrote: On Apr 14, 11:18 pm, Charles E Campbell Jr [EMAIL PROTECTED] wrote: The primary disadvantage is that effectively writing a new yacc/bison is not a small task. I have a real thick book about writing a yacc-like parser somewhere; if anyone's interested,

Re: GSOC: On-the-fly Code Checking for Vim - Challenges

Birgi Tamersoy wrote: Hey everybody, Apparently many students (like me) are interested in this project. So, I decided to start a new thread where we can talk about the challenges in the project and how to solve them. I went over previous posts to include all the related ideas in this new

Re: GSOC: On-the-fly Code Checking for Vim - Challenges

On Sat, Apr 12, 2008 at 8:11 PM, Birgi Tamersoy [EMAIL PROTECTED] wrote: I really think that by the end of this August we can have an on-the- fly code checker which will be used by a majority of the community. I'm not sure how many people are interested in on-the-fly compilation. I know I'm

Re: GSOC: On-the-fly Code Checking for Vim - Challenges

Hey everybody, I'm not really because I program mainly in C++, and my experience demonstrates that after the first error it is not uncommon to have the compiler completely lost. Thus I know this will be a very complex task, and I'm not sure it can be done. After your posts I made a small

RE: GSOC: On-the-fly Code Checking for Vim - Challenges

hermitte wrote: I'm not sure how many people are interested in on-the-fly compilation. I'm not really because I program mainly in C++, and my experience demonstrates that after the first error it is not uncommon to have the compiler completely lost. Thus I know this will be a very

RE: GSOC: On-the-fly Code Checking for Vim - Challenges

John Beckett [EMAIL PROTECTED] wrote: Consider the issue recently raised by Dominique Pelle: People editing C++ code would really appreciate a bit more intelligence applied to the tags feature so that Ctrl-] would try a bit harder to jump to the correct overloaded name. That would be tricky,

Re: GSOC: On-the-fly Code Checking for Vim - Challenges

Using a *built-in parser* is solution emphasized by Charles E. Campbell Jr in a related post. A parser would be perfect for syntax- checking, but I think the code checker should also detect errors like a misspelled library name. At least for C, you could use the clang C frontend (