| From: | "Inoue, Hiroshi" <inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: Source code cleanup |
| Date: | 2013-01-10 03:58:30 |
| Message-ID: | 50EE3C66.1080801@tpf.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Hi Heikki,
(2013/01/09 3:25), Heikki Linnakangas wrote:
> I'm getting a bunch of compiler warnings when I compile the latest
> psqlodbc sources from CVS. I spent some time cleaning those up.
>
> I also got access to a report of a Coverity scan over psqlodbc source
> tree. That found a bunch of additional issues, some of which were
> genuine (minor) bugs. I'm still in the process of going through the
> report, but I fixed some bugs already.
Thanks.
>
> I also wrote a small regression test suite to test with. It only tests a
> few of the ODBC functions at the moment, but it's better than nothing,
> and it can be easily extended. What do others use for testing psqlodbc?
>
> I pushed the result to a git repository at
> git(at)github(dot)com:hlinnaka/psqlodbc.git. It contains the psqlodbc CVS
> history, as converted by git cvsimport, and my changes as commits on top
> of that.
I would check the git repository.
> I can also send the changes as patches if that's preferred. Let
> me know how to proceed.
>
> - Heikki
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2013-01-11 03:40:17 | Re: Source code cleanup |
| Previous Message | Heikki Linnakangas | 2013-01-08 18:25:41 | Source code cleanup |