Hi Aleksey,

I don’t know if I understood you completely, rgenstat works by parsing c/cpp source files not header files. What do you mean with “standard function header”?

If we are seriously going to use it I would like to make some slightly modifications to it to make it more powerful but would require help from someone with more experience than me writing parsers in C.

Regards,

/Marc

---

From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Aleksey Bragin
Sent: Friday, November 09, 2007 9:20 PM
To: ReactOS Development List
Subject: Re: [ros-dev] Tracking implementation API status

I support that, though some modifications should be required, because in the kernel a standard function header [should be]/is used. If it's able to parse that header too (provided it contains the @implemented/@unimplemented), then it's great.

WBR,

Aleksey Bragin.

On Nov 9, 2007, at 8:29 PM, Marc Piulachs wrote:

As most of you know, Casper created a small tool rgenstat (tools/rgenstat) that is able to parse source code for modules specified on apistatus.lst seeking for public APIs decorated with the @implemented or @unimplemented C comment. Rgenstat when invoked typing “make rgenstat” it produces an xml file containing all the functions and it’s current implementation status. With this database we can do all sorts of automatic compatibility reports . see for example wine’s equivalent http://www.winehq.org/site/status or http://www.codexchange.net/roslib generated from incomplete reactos data , (work in progress)

As it easy and not intrusive I would suggest using this feature to kernel and core developers. Fireball , GreatLord , Jim , what do you think about that ?

/Marc