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

2008-04-12 Fir de Conversatie Nico Weber
> 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 ( clang.l

Re: Updated floating point patch

2008-04-12 Fir de Conversatie Tony Mechelynck
On 12/04/08 22:29, Mikolaj Machowski wrote: > Dnia Saturday 12 of April 2008, Tony Mechelynck napisał: >> On 12/04/08 20:29, Mikolaj Machowski wrote: >>> Dnia Saturday 12 of April 2008, Bram Moolenaar napisał: Here is an update for the floating point patch. The 'g' argument for printf()

Re: Updated floating point patch

2008-04-12 Fir de Conversatie Mikolaj Machowski
Dnia Saturday 12 of April 2008, Tony Mechelynck napisał: > On 12/04/08 20:29, Mikolaj Machowski wrote: > > Dnia Saturday 12 of April 2008, Bram Moolenaar napisał: > >> Here is an update for the floating point patch. The 'g' argument for > >> printf() was implemented and a few bug fixes. > >> > >>

Re: Updated floating point patch

2008-04-12 Fir de Conversatie Tony Mechelynck
On 12/04/08 20:29, Mikolaj Machowski wrote: > Dnia Saturday 12 of April 2008, Bram Moolenaar napisał: >> Here is an update for the floating point patch. The 'g' argument for >> printf() was implemented and a few bug fixes. >> >> This is to be applied to the original source code, without the older

Re: Updated floating point patch

2008-04-12 Fir de Conversatie Tony Mechelynck
On 12/04/08 19:57, Steve Hall wrote: > On Sat, 2008-04-12 at 16:58 +0200, Bram Moolenaar wrote: >> I would still like feedback on the format of floating point numbers: >> >>&123.456 >>&1.23e-3 > > I don't understand the ampersand, why not something more mnemonic: > > f123.456 > .

Re: Updated floating point patch

2008-04-12 Fir de Conversatie Mikolaj Machowski
Dnia Saturday 12 of April 2008, Bram Moolenaar napisał: > Here is an update for the floating point patch. The 'g' argument for > printf() was implemented and a few bug fixes. > > This is to be applied to the original source code, without the older > floating point patch. > One thing: let a = &1.

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

2008-04-12 Fir de Conversatie Birgi Tamersoy
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 thread. Here are a few initia

Re: Updated floating point patch

2008-04-12 Fir de Conversatie Steve Hall
On Sat, 2008-04-12 at 16:58 +0200, Bram Moolenaar wrote: > > I would still like feedback on the format of floating point numbers: > > &123.456 > &1.23e-3 I don't understand the ampersand, why not something more mnemonic: f123.456 .123.456 f.123.456 .f123.456 +123.456 --

Re: Updated floating point patch

2008-04-12 Fir de Conversatie Tony Mechelynck
On 12/04/08 16:58, Bram Moolenaar wrote: > Here is an update for the floating point patch. The 'g' argument for > printf() was implemented and a few bug fixes. > > This is to be applied to the original source code, without the older > floating point patch. > > I would still like feedback on the f