Date: Sat, 28 May 2011 01:38:11 -0500 From: Zhihao Yuan <lichray@gmail.com> To: soc-status@freebsd.org Cc: Alexander Leidinger <alexander@leidinger.net> Subject: [nvi-iconv]Weekly status report Message-ID: <BANLkTimd3afK5y4ncJS9pqj8oR=xCeZXmg@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
To whom may concerned: Before talking about the coding stuff, let me explain something about my schedule. According to my proposal, I should start this project at 5/16. But I was struggling with the paper works to get my CPT (working permission) during that week, so I will just move my schedule to the regular GSoC time. For the first week, I planed to read and clean up the nvi-1.79 code. I moved the code from contrib to usr.bin since I'm forking the project for FreeBSD. I updated the autotools, and added a HAVE_TERM_H test to solve the <term.h> problem (finally, according the the commit history). Other misc changes can be seen from the svn log. One of the problems I met so far is the CHAR_T usage in nvi. In nvi, it's a typedef to unsigned char, which is used to represent the command (to be able to map them in arrays). But in nvi-1.81, CHAR_T (wchar_t) is used to represent the input text. Before deciding whether to use wchar_t in this project, I hope I can trace the char type usage more deeply and can hopefully get rid of the related warnings. -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___________________________________________________ 4BSD -- http://4bsd.biz/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTimd3afK5y4ncJS9pqj8oR=xCeZXmg>